Date: Sat, 3 Jan 2026 22:09:34 +0100 From: A FreeBSD User <freebsd@walstatt-de.de> To: Gleb Smirnoff <glebius@freebsd.org> Cc: FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: CURRENT: kernel panic in IPFW while stopping jails Message-ID: <20260103220845.5c9bb4b6@thor.sb211.local> In-Reply-To: <aVloGMy4vCGUI0SZ@cell.glebi.us> References: <aVQFvirQiq9_2ZgB@cell.glebi.us> <6ed6434fce515fb9dab694bb649da95b@riseup.net> <aVVkyDb-EvIA6kig@cell.glebi.us> <A81BE148-9622-461F-9D37-5B1CC62C90B7@gushi.org> <39862682-0F6D-4563-A9CE-276CF61556B8@gushi.org> <aVloGMy4vCGUI0SZ@cell.glebi.us>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] Am Tage des Herren Sat, 3 Jan 2026 11:03:52 -0800 Gleb Smirnoff <glebius@freebsd.org> schrieb: > On Fri, Jan 02, 2026 at 12:57:52PM -0600, Dan Mahoney (ports) wrote: > D> Glebius > D> > D> Confirmed, this now fixes the issue (which apparently involves auto-numbered rules and > D> the "log" keyword). > D> > D> At some point, I'll make sure I have the process down to capture a core dump more easily > D> for you. Welcome to the fun of tracking MAIN :) > D> > D> Thanks for all your quick work. Please do let me know then this change makes it into > D> git. > > The change itself surfaced a problem with my bpf patch as well as with some > locking design of ipfw. If you use the patch as is it will print warnings with > WITNESS, and these warnings are legitimate. I'm working on a better solution. I > might check in the patch as is to prevent people with autonumbered logging > rules stepping on the panic meanwhile. > ... much appreciated, thanks. -- A FreeBSD user [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQRQheDybVktG5eW/1Kxzvs8OqokrwUCaVmFqQAKCRCxzvs8Oqok r1XEAP9UOuFUQbLtj5+pRh6V1oVgkol3FDevQnzf9CCiQfT7owD+LgAIoXAwn6Nq ytAFH+mH/rW5wzKcVNCo4wtwVE4QWgI= =ww1G -----END PGP SIGNATURE-----home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20260103220845.5c9bb4b6>