Date: Thu, 1 Jan 2026 19:57:43 -0600 From: "Dan Mahoney (ports)" <freebsd@gushi.org> To: Gleb Smirnoff <glebius@freebsd.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: <A81BE148-9622-461F-9D37-5B1CC62C90B7@gushi.org> In-Reply-To: <aVVkyDb-EvIA6kig@cell.glebi.us> References: <aVQFvirQiq9_2ZgB@cell.glebi.us> <6ed6434fce515fb9dab694bb649da95b@riseup.net> <aVVkyDb-EvIA6kig@cell.glebi.us>
index | next in thread | previous in thread | raw e-mail
Building now. Sorry for delay, I've been doing a long cross-country drive. -Dan > On Dec 31, 2025, at 12:00 PM, Gleb Smirnoff <glebius@freebsd.org> wrote: > > On Wed, Dec 31, 2025 at 03:06:38AM +0000, Alastair Hogge wrote: > A> > I have found the problem, thanks to Alastair for a core file. > A> > > A> > The problem affects rules with automatic rule numbers and logging. > A> > > A> > The attached patch should fix the problem, but it is not a final version. > A> > A> Is there a special patch incantation I should be aware of? I have tried > A> the patch against both 8e951583936980909d34a6104ace781541fb62b1[1], and > A> 4fecc8e3fe9408621429777b1028c9afb83c3925[2], and observed the following: > ... > A> 3 out of 3 hunks failed while patching sys/netpfil/ipfw/ip_fw_sockopt.c > > The only explanation I have is that your email agent has mangled the patch. > > A> > Dan & Alastair, if any of you can confirm that the patch heals your setup - I > A> > will appreciate. > A> > A> I manually patched in your work, and was able to boot a sync'd > A> -CURRENT[2], with logging counters re-enabled, there has been no panics > A> for ~20 minutes now. > > Great! The patch as is isn't final. I will find out something better after > the holidays. > > -- > Gleb Smirnoffhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A81BE148-9622-461F-9D37-5B1CC62C90B7>