Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 27 Sep 2017 19:10:35 +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-CPB1vOxU0F@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 #23 from Kristof Provost <kp@freebsd.org> ---
(In reply to hlh from comment #22)
Did you take that '# pfctl -si' before attempting any of the workarounds? It
shows you've got 31 states, I don't see how you'd hit the state limit that =
way.

It might be interesting to keep dtrace running while you run the workaround=
.=20
Everything I see so far suggests that we're stuck in the rw_sleep() (which =
was
changed to an sx_sleep() in CURRENT), but that makes no sense. I don't see =
how
that could happen, or how the workaround could help there.

Can you confirm you're not running low on memory? That might conceivably al=
so
trigger the 'PF states limit reached' warning (although I'd expect to see m=
any
other warnings too), but I'm not sure how that would look like a frozen pur=
ge
thread.

--=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-CPB1vOxU0F>