Glebius Confirmed, this now fixes the issue (which apparently involves auto-numbered rules and the "log" keyword).
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 :) Thanks for all your quick work. Please do let me know then this change makes it into git. -Dan > On Jan 1, 2026, at 7:57 PM, Dan Mahoney (ports) <[email protected]> wrote: > > 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 <[email protected]> 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 Smirnoff > >
