https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235097
Bjoern A. Zeeb <b...@freebsd.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |b...@freebsd.org
Summary|ci runs failing with panic |ci runs panic with
|in IPv6 code with |use-after-free when running
|use-after-free in |sys/netpfil/pf/nat tests
|epair/pfctl when running |
|sys/netpfil/pf/nat tests |
--- Comment #5 from Bjoern A. Zeeb <b...@freebsd.org> ---
(In reply to Li-Wen Hsu from comment #1)
Why do you think these two revision numbers have introduced the problem?
Because if they did the search pattern is very small. Just trying to
understand.
(In reply to Kristof Provost from comment #4)
Depending on the answer above it could be anything (a x++, refcount, ..). It
doesn't have to be a counter(9) increment. It could also be anywhere in the
code, not necessarily the network stack where this happens. It's just that the
test cases run a lot of network stack code, which means it's most likely to be
the next allocation that then finds the modified memory.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
