Page MenuHomeFreeBSD

pf tests: Lower chances of false positives for mbuf:inet6_in_mbuf_len
ClosedPublic

Authored by igoro on Oct 18 2024, 2:02 PM.
Tags
None
Referenced Files
F167181293: D47175.id145107.diff
Wed, Aug 19, 5:05 PM
F167118676: D47175.id.diff
Wed, Aug 19, 6:14 AM
Unknown Object (File)
Tue, Aug 18, 11:17 AM
Unknown Object (File)
Wed, Aug 12, 8:10 PM
Unknown Object (File)
Wed, Aug 12, 3:06 PM
Unknown Object (File)
Wed, Aug 12, 12:13 AM
Unknown Object (File)
Mon, Aug 10, 10:57 AM
Unknown Object (File)
Mon, Aug 10, 9:23 AM

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

igoro requested review of this revision.Oct 18 2024, 2:02 PM

This is the outcome of my analysis of the following CI test failure: https://ci.freebsd.org/view/Test/job/FreeBSD-main-amd64-test/25598/testReport/junit/sys.netpfil.pf/mbuf/inet6_in_mbuf_len/.
An extra 2001:db8::1 → 2001:db8::2 ICMPv6 Neighbor Advertisement 2001:db8::1 (sol) packet can appear. If it's sent after the net.dummymbuf.hits value is compared then it does not impact the results, but it may happen before.

I would have guessed it'd be MLD packets, but neighbour unreachability detection could also be causing this.

Approved.

This revision is now accepted and ready to land.Oct 18 2024, 2:18 PM