Date: Sun, 22 Oct 2017 20:05:13 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-pf@FreeBSD.org Subject: [Bug 222126] pf is not clearing expired states Message-ID: <bug-222126-17777-ls1EKaltox@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-222126-17777@https.bugs.freebsd.org/bugzilla/> References: <bug-222126-17777@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222126 --- Comment #37 from Kristof Provost <kp@freebsd.org> --- I do not understand this at all. There is no reason for the purge thread to= get stuck. There's also no reason for it apparently having run 7 times between freezing and when you restart the dtrace. (That's based on the purge_idx va= lue logged by the expired_states probe. 23544 - 21255 =3D=3D 327 * 7. (Please just don't stop it at all while you're performing the workaround. There's no reason for it, and stopping it runs the risk of missing interest= ing information). It still looks like we just don't wake up from the sx_sleep(pf_purge_thread, &pf_end_lock, ...) call, but that makes no sense. The only way for that to happen is if someone would be holding the pf_end_lock, but that lock is only taken when the pf module is unloaded (and by the purge thread, obviously). Do you see other strange behaviour on the system? If there's something wrong with the sleep/lock infrastructure I'd expect to see other strange things. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-222126-17777-ls1EKaltox>