Date: Sat, 3 Jan 2026 11:03:52 -0800 From: Gleb Smirnoff <glebius@freebsd.org> To: "Dan Mahoney (ports)" <freebsd@gushi.org> Cc: Alastair Hogge <agh@riseup.net>, FreeBSD User <freebsd@walstatt-de.de>, Ronald Klop <ronald-lists@klop.ws>, FreeBSD CURRENT <freebsd-current@freebsd.org> Subject: Re: CURRENT: kernel panic in IPFW while stopping jails Message-ID: <aVloGMy4vCGUI0SZ@cell.glebi.us> In-Reply-To: <39862682-0F6D-4563-A9CE-276CF61556B8@gushi.org> 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>
index | next in thread | previous in thread | raw e-mail
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 the "log" keyword). D> D> At some point, I'll make sure I have the process down to capture a core dump more easily 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 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. -- Gleb Smirnoffhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aVloGMy4vCGUI0SZ>