On 20/09/17 19:25, Visa Hankala wrote:
On Wed, Sep 20, 2017 at 02:26:56PM +0300, Kapetanakis Giannis wrote:
I got this panic today after ping -R
I don't run pfsync
# ping -R www.google.com
panic: kernel diagnostic assertion "m0->m_flags & M_PKTHDR" failed: file
"/usr/src/sys/kern/uipc_mbuf.c", line 1344splassert: pfsync_update_state: want 1 have 256
pStopped at db_enter+0x5: popq %rbp
TID PID UID PRFLAGS PFLAGS CPU COMMAND
*299140 12380 51 0x33 0 2 ping
422116 15532 0 0x14000 0x200 1 softnet
db_enter() at db_enter+0x5
panic() at panic+0x128
__assert(ffffffff81020a74,ffff80002692f4a0,0,1) at __assert+0x24
m_dup_pkt(ffffff010c77caf8,1,ffffff00baab064b) at m_dup_pkt+0x225
ip_pcbopts(1,ffffff00baab0600) at ip_pcbopts+0x138
sosetopt(ffffff010947b018,ffff800026798d68,ffff80002692f5f0,ffffff00baab0600) a
t sosetopt+0xd0
sys_setsockopt(ffff80002692f680,690,ffff800026798d68) at sys_setsockopt+0x13d
syscall() at syscall+0x270
--- syscall (number 105) ---
end of kernel
end trace frame: 0x7f7ffffbf230, count: 7
Thank you for reporting this. A fix for the bug has been committed.
Thanks for the quick fix :)
tested and no more panic
G
