Date: Sat, 22 May 2021 09:42:54 +0000 From: bugzilla-noreply@freebsd.org To: pf@FreeBSD.org Subject: [Bug 255971] FreeBSD 13.0 Stable r3822450 hangs with error pfctl: DIOCGETRULE: Cannot allocate memory Message-ID: <bug-255971-16861-35lFCpaxxt@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-255971-16861@https.bugs.freebsd.org/bugzilla/> References: <bug-255971-16861@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=3D255971 Kristof Provost <kp@freebsd.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|New |Open Assignee|pf@FreeBSD.org |kp@freebsd.org --- Comment #14 from Kristof Provost <kp@freebsd.org> --- Okay, I'm starting to make sense of this. pfctl -sr leaks memory on every invocation. I was confused by DIOCGETRULE, because it's not that call. It's DIOCGETRULENV, but the pfctl error message= is still DIOCGETRULE. That also means that 13.0 is not affected (yay!). DIOCGETRULENV is relative= ly new code, but I don't see an obvious leak path right now. At least it's trivial to reproduce, so we'll get there in the next couple of days. You'll probably want to stop calling `pfctl -sr` or `pfctl -sa` for now. That'll mitigate your freezing issue until we can figure the leak out and f= ix it. --=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-255971-16861-35lFCpaxxt>