[Bug 148807] [panic] "panic: sbdrop" and "panic: sbsndptr: sockbuf _ and mbuf _ clashing" (8.1-RELEASE/10.1-STABLE/11-CURRENT)

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=148807

--- Comment #29 from Robert Watson <rwatson at FreeBSD.org> ---
Just a quick comment in light of recent notes on this PR: the panic being seen
is as a result of a kernel self-check that occurs on socket close, and likely
reports on a bug that triggered some substantial time earlier (milliseconds,
seconds, minutes, hours, days, or even weeks earlier), and reports on a class
of problems rather than detecting a specific bug. It's entirely likely that the
problem reported more recently is not the same bug as those reported previously
with the same panic message -- rather, a similar bug with the same kernel
self-check detecting it.

In the past, this self-check has most frequently fired as a result of either
bugs in the socket-buffer code (although I think none recently), or
device-driver bugs involving modifications to the mbuf chain after submitting
the mbuf to the network stack (e.g., due to concurrency bugs in the device
driver). It can also occur in use-after-free scenarios, as a result of protocol
bugs, etc.

On the whole, my intuition is towards a device-driver bug based on past
experience. Could you paste in the output of "dmesg" and "ifconfig -a" from the
host to give a bit more information on its configuration?

-- 
You are receiving this mail because:
You are the assignee for the bug.