Home - Waterfall Grid T-Grid Console Builders Recent Builds Buildslaves Changesources - JSON API - About

Builder tcpdump-solaris10-sparcv9 Build #6117

Results:

Build successful

SourceStamp:

Projecttcpdump
Repositoryhttps://git.tcpdump.org/tcpdump
Branchmaster
Revisionbee4d998990d79b29427c0077d17a314536d7115
Got Revisionbee4d998990d79b29427c0077d17a314536d7115
Changes3 changes

BuildSlave:

unstable10s

Reason:

The SingleBranchScheduler scheduler named 'schedule-tcpdump-solaris10-sparcv9' triggered this build

Steps and Logfiles:

  1. git update ( 14 secs )
    1. stdio
  2. shell Set developer mode ( 0 secs )
    1. stdio
  3. shell_1 './autogen.sh' ( 18 secs )
    1. stdio
  4. shell_2 configure ( 2 mins, 5 secs )
    1. stdio
  5. shell_3 gmake ( 8 mins, 32 secs )
    1. stdio
  6. shell_4 check ( 1 mins, 0 secs )
    1. stdio
    2. failure-outputs.txt

Build Properties:

NameValueSource
branch master Build
builddir /export/home/buildbot-unstable10s/slave/tcpdump-solaris10-sparcv9 slave
buildername tcpdump-solaris10-sparcv9 Builder
buildnumber 6117 Build
codebase Build
got_revision bee4d998990d79b29427c0077d17a314536d7115 Git
project tcpdump Build
repository https://git.tcpdump.org/tcpdump Build
revision bee4d998990d79b29427c0077d17a314536d7115 Build
scheduler schedule-tcpdump-solaris10-sparcv9 Scheduler
slavename unstable10s BuildSlave
workdir /export/home/buildbot-unstable10s/slave/tcpdump-solaris10-sparcv9 slave (deprecated)

Forced Build Properties:

NameLabelValue

Responsible Users:

  1. Maxim Mikityanskiy

Timing:

StartMon Feb 2 18:06:30 2026
EndMon Feb 2 18:18:43 2026
Elapsed12 mins, 12 secs

All Changes:

:

  1. Change #256834

    Category tcpdump
    Changed by Maxim Mikityanskiy <maximohnoyoudont@isovalent.com>
    Changed at Mon 02 Feb 2026 18:00:51
    Repository https://git.tcpdump.org/tcpdump
    Project tcpdump
    Branch master
    Revision b43797a47d7a9a0a2e3b61d9d911763e1df81cbe

    Comments

    tests: Add coverage for GSO/TSO and BIG TCP
    This commit adds coverage that affirms the current behavior of tcpdump
    when it parses packets captured in Linux with aggregation offloads
    enabled (such as GRO, GSO, TSO and BIG TCP).
    
    New tests include:
    
    1. GRO/GSO/TSO TCP packets. These have ip_len (IPv4) or payload_len
    (IPv6) set to a value bigger than MTU, but smaller than 64k (fits the
    width of the length field, which is 16 bits).
    
    2. BIG TCP packets, as currently implemented in Linux. These aggregated
    packets are larger than 64k. In IPv4, ip_len is just set to 0. In IPv6,
    payload_len is also set to 0, and the real length of the payload is
    indicated in the Jumbo option of the Hop-by-hop extension header,
    immediately following the IPv6 header.
    
    3. A corner case: a small (<64k) IPv4 packet with ip_len set to 0. Turns
    out that both tcpdump and wireshark treat such packets as valid,
    regardless of the transport protocol, simply printing a message that TSO
    was presumed. While my tests show that TSO actually fills in the correct
    (non-zero) value into the ip_len field, the test suite already contains
    a test called ipv4_tcp_http_xml_tso with a 2030-byte TCP/IPv4 packet
    that has ip_len = 0, but it's treated as a valid packet. The packet was
    captured in 2012, and the exact circumstances of why it has a zero
    ip_len are unclear to me, but if such packets are considered valid by
    both tcpdump and wireshark, I'm extending the coverage by adding an ICMP
    packet with ip_len = 0, which was manually crafted.
    
    Signed-off-by: Maxim Mikityanskiy <maxim@isovalent.com>

    Changed files

    • tests/TESTLIST
    • tests/bigtcp-ipv4.out
    • tests/bigtcp-ipv4.pcap
    • tests/bigtcp-ipv6-hbh.out
    • tests/bigtcp-ipv6-hbh.pcap
    • tests/gso-ipv4.out
    • tests/gso-ipv4.pcap
    • tests/gso-ipv6.out
    • tests/gso-ipv6.pcap
    • tests/icmp-length-zero.out
    • tests/icmp-length-zero.pcap
  2. Change #256835

    Category tcpdump
    Changed by Maxim Mikityanskiy <maximohnoyoudont@isovalent.com>
    Changed at Mon 02 Feb 2026 18:00:51
    Repository https://git.tcpdump.org/tcpdump
    Project tcpdump
    Branch master
    Revision d51acf66a32af3067bab340839646709193e626e

    Comments

    ipv6: Support new BIG TCP without HBH
    Currently, BIG TCP IPv6 inserts a hop-by-hop extension header with a
    jumbo payload option to reflect the real length of the packet bigger
    than 65535 bytes. New kernels will drop this extension header and just
    calculate the packet length from skb->len, like it's currently done for
    BIG TCP IPv4.
    
    Reflect the future kernel change in tcpdump and support parsing such
    packets.
    
    BIG TCP only sets payload_len = 0 when the actual payload length is
    65536 or more. Check that explicitly, so that smaller packets with
    payload_len = 0 are still considered invalid, like in the test called
    icmpv6-length-zero. Check the transport protocol (next header) to be TCP
    or UDP because TCP may be inner in an encapsulated packet, e.g., in
    UDP-based tunnels, such as VXLAN and GENEVE.
    
    Signed-off-by: Maxim Mikityanskiy <maxim@isovalent.com>

    Changed files

    • print-ip6.c
  3. Change #256836

    Category tcpdump
    Changed by Maxim Mikityanskiy <maximohnoyoudont@isovalent.com>
    Changed at Mon 02 Feb 2026 18:00:51
    Repository https://git.tcpdump.org/tcpdump
    Project tcpdump
    Branch master
    Revision bee4d998990d79b29427c0077d17a314536d7115

    Comments

    tests: Add coverage for new BIG TCP cases
    This commit adds tests for BIG TCP IPv6 without a hop-by-hop header, as
    announced in the previous commit, and also for encapsulated BIG TCP
    packets: TCP inside a VXLAN or GENEVE tunnel, for all combinations of
    outer/inner IPv4/IPv6.
    
    Besides that, this commit adds tests for similar tunneled packets, but
    non-BIG TCP, i.e. smaller than 64k, regular GSO. These packets don't set
    ip_len or payload_len to 0.
    
    Signed-off-by: Maxim Mikityanskiy <maxim@isovalent.com>

    Changed files

    • tests/TESTLIST
    • tests/bigtcp-ipv4-geneve-ipv4.out
    • tests/bigtcp-ipv4-geneve-ipv4.pcap
    • tests/bigtcp-ipv4-geneve-ipv6.out
    • tests/bigtcp-ipv4-geneve-ipv6.pcap
    • tests/bigtcp-ipv4-vxlan-ipv4.out
    • tests/bigtcp-ipv4-vxlan-ipv4.pcap
    • tests/bigtcp-ipv4-vxlan-ipv6.out
    • tests/bigtcp-ipv4-vxlan-ipv6.pcap
    • tests/bigtcp-ipv6-geneve-ipv4.out
    • tests/bigtcp-ipv6-geneve-ipv4.pcap
    • tests/bigtcp-ipv6-geneve-ipv6.out
    • tests/bigtcp-ipv6-geneve-ipv6.pcap
    • tests/bigtcp-ipv6-vxlan-ipv4.out
    • tests/bigtcp-ipv6-vxlan-ipv4.pcap
    • tests/bigtcp-ipv6-vxlan-ipv6.out
    • tests/bigtcp-ipv6-vxlan-ipv6.pcap
    • tests/bigtcp-ipv6.out
    • tests/bigtcp-ipv6.pcap
    • tests/gso-ipv4-geneve-ipv4.out
    • tests/gso-ipv4-geneve-ipv4.pcap
    • tests/gso-ipv4-geneve-ipv6.out
    • tests/gso-ipv4-geneve-ipv6.pcap
    • tests/gso-ipv4-vxlan-ipv4.out
    • tests/gso-ipv4-vxlan-ipv4.pcap
    • tests/gso-ipv4-vxlan-ipv6.out
    • tests/gso-ipv4-vxlan-ipv6.pcap
    • tests/gso-ipv6-geneve-ipv4.out
    • tests/gso-ipv6-geneve-ipv4.pcap
    • tests/gso-ipv6-geneve-ipv6.out
    • tests/gso-ipv6-geneve-ipv6.pcap
    • tests/gso-ipv6-vxlan-ipv4.out
    • tests/gso-ipv6-vxlan-ipv4.pcap
    • tests/gso-ipv6-vxlan-ipv6.out
    • tests/gso-ipv6-vxlan-ipv6.pcap