[Bug 284457] periodic pf panic on busy jailhost

[email protected]
Newsgroups gmane.os.freebsd.devel.pf4freebsd
Message-ID <[email protected]/bugzilla/>
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284457

--- Comment #9 from Thomas Steen Rasmussen / Tykling <[email protected]> ---
(kgdb) backtrace
#0  __curthread () at /usr/src/sys/amd64/include/pcpu_aux.h:53
#1  doadump (textdump=<optimized out>) at /usr/src/sys/kern/kern_shutdown.c:394
#2  0xffffffff80bf5d1e in kern_reboot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:482
#3  0xffffffff80bf61da in vpanic (fmt=0xffffffff8120ec72 "%s",
ap=ap@entry=0xfffffe01aee8bc60) at /usr/src/sys/kern/kern_shutdown.c:921
#4  0xffffffff80bf5ff3 in panic (fmt=<unavailable>) at
/usr/src/sys/kern/kern_shutdown.c:845
#5  0xffffffff810b3169 in trap_fatal (frame=0xfffffe01aee8bd40, eva=3358108780)
at /usr/src/sys/amd64/amd64/trap.c:940
#6  0xffffffff810b31b6 in trap_pfault (frame=<unavailable>, usermode=false,
signo=<optimized out>, ucode=<optimized out>) at
/usr/src/sys/amd64/amd64/trap.c:759
#7  <signal handler called>
#8  0xffffffff82f30e7f in pf_state_key_detach (s=0xfffff80206395750, idx=1) at
/usr/src/sys/netpfil/pf/pf.c:1414
#9  pf_detach_state (s=s@entry=0xfffff80206395750) at
/usr/src/sys/netpfil/pf/pf.c:1380
#10 0xffffffff82f324f5 in pf_unlink_state (s=s@entry=0xfffff80206395750,
flags=flags@entry=1) at /usr/src/sys/netpfil/pf/pf.c:2350
#11 0xffffffff82f31bcd in pf_purge_expired_states (i=120411, maxcheck=109) at
/usr/src/sys/netpfil/pf/pf.c:2401
#12 0xffffffff82f31a2b in pf_purge_thread (unused=<optimized out>) at
/usr/src/sys/netpfil/pf/pf.c:2145
#13 0xffffffff80bb159f in fork_exit (callout=0xffffffff82f318f0
<pf_purge_thread>, arg=0x0, frame=0xfffffe01aee8bf40) at
/usr/src/sys/kern/kern_fork.c:1151
#14 <signal handler called>
#15 0x000018c35cb7e32a in ?? ()
Backtrace stopped: Cannot access memory at address 0x18c35a558fc8
(kgdb)

-- 
You are receiving this mail because:
You are the assignee for the bug.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.