From nobody Fri Jan 23 23:47:18 2026 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4dyZNV5ZWmz6PxgH for ; Fri, 23 Jan 2026 23:47:22 +0000 (UTC) (envelope-from agh@riseup.net) Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mx1.riseup.net", Issuer "R12" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4dyZNT23S7z4169; Fri, 23 Jan 2026 23:47:21 +0000 (UTC) (envelope-from agh@riseup.net) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=riseup.net header.s=squak header.b=SMEzISAV; dmarc=pass (policy=none) header.from=riseup.net; spf=pass (mx1.freebsd.org: domain of agh@riseup.net designates 198.252.153.129 as permitted sender) smtp.mailfrom=agh@riseup.net Received: from fews01-sea.riseup.net (fews01-sea-pn.riseup.net [10.0.1.109]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx1.riseup.net (Postfix) with ESMTPS id 4dyZNR1DLVzDsBD; Fri, 23 Jan 2026 23:47:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=riseup.net; s=squak; t=1769212039; bh=jcXE+UxxWNu91qHzr/GxKZ5Dap+nBbnzpTFj1B63kh4=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=SMEzISAVHxRHDzaAuXMKlYFyfoQFDllSCCi3DCJ4oaFlk0l4As/drOgV9vHwmlZO0 C+NEOeMEMVSii41wnEBo06zSd17fE/ZU1yrK9QMPbiwqgh08hPCJQDrKtU75Q9Gqff G90+YMoH3QpA7HYoRg73ud3Ay+HucLecITWyfkRo= X-Riseup-User-ID: CFEF9074A612E5B1E75ABBF4187E8213CC1CF48F47F69ED5BF2BFC57D679AA0F Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews01-sea.riseup.net (Postfix) with ESMTPSA id 4dyZNQ2g76z1yvQ; Fri, 23 Jan 2026 23:47:18 +0000 (UTC) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Date: Fri, 23 Jan 2026 23:47:18 +0000 From: Alastair Hogge To: Gleb Smirnoff Cc: "Dan Mahoney (ports)" , FreeBSD User , Ronald Klop , FreeBSD CURRENT Subject: Re: CURRENT: kernel panic in IPFW while stopping jails In-Reply-To: References: <6ed6434fce515fb9dab694bb649da95b@riseup.net> <39862682-0F6D-4563-A9CE-276CF61556B8@gushi.org> Message-ID: <444517b14f72570b20b600a31977949f@riseup.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.20 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[riseup.net,none]; R_DKIM_ALLOW(-0.20)[riseup.net:s=squak]; R_SPF_ALLOW(-0.20)[+a:mx1.riseup.net]; RCVD_IN_DNSWL_LOW(-0.10)[198.252.153.129:from]; MIME_GOOD(-0.10)[text/plain]; RWL_MAILSPIKE_GOOD(-0.10)[198.252.153.129:from]; RCVD_TLS_ALL(0.00)[]; TO_DN_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; RECEIVED_HELO_LOCALHOST(0.00)[]; MIME_TRACE(0.00)[0:+]; DKIM_TRACE(0.00)[riseup.net:+]; MISSING_XM_UA(0.00)[]; ASN(0.00)[asn:16652, ipnet:198.252.153.0/24, country:US]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; DWL_DNSWL_NONE(0.00)[riseup.net:dkim]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCPT_COUNT_FIVE(0.00)[5] X-Rspamd-Queue-Id: 4dyZNT23S7z4169 On 2026-01-17 12:12, Gleb Smirnoff wrote: > Hi, Hello Gleb, > I have pushed all necessary changes to main, that properly address the panic > with auto-numbered rules with the "log" keyword, that was introduced in the > late December. Very sorry that it took so long! Sync'd, updated, and restored ipfw config. No problems here. Thanks for your efforts. > 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. > D> > D> -Dan > D> > D> > On Jan 1, 2026, at 7:57 PM, Dan Mahoney (ports) wrote: > D> > > D> > Building now. Sorry for delay, I've been doing a long cross-country drive. > D> > > D> > -Dan > D> > > D> >> On Dec 31, 2025, at 12:00 PM, Gleb Smirnoff wrote: > D> >> > D> >> On Wed, Dec 31, 2025 at 03:06:38AM +0000, Alastair Hogge wrote: > D> >> A> > I have found the problem, thanks to Alastair for a core file. > D> >> A> > > D> >> A> > The problem affects rules with automatic rule numbers and logging. > D> >> A> > > D> >> A> > The attached patch should fix the problem, but it is not a final version. > D> >> A> > D> >> A> Is there a special patch incantation I should be aware of? I have tried > D> >> A> the patch against both 8e951583936980909d34a6104ace781541fb62b1[1], and > D> >> A> 4fecc8e3fe9408621429777b1028c9afb83c3925[2], and observed the following: > D> >> ... > D> >> A> 3 out of 3 hunks failed while patching sys/netpfil/ipfw/ip_fw_sockopt.c > D> >> > D> >> The only explanation I have is that your email agent has mangled the patch. > D> >> > D> >> A> > Dan & Alastair, if any of you can confirm that the patch heals your setup - I > D> >> A> > will appreciate. > D> >> A> > D> >> A> I manually patched in your work, and was able to boot a sync'd > D> >> A> -CURRENT[2], with logging counters re-enabled, there has been no panics > D> >> A> for ~20 minutes now. > D> >> > D> >> Great! The patch as is isn't final. I will find out something better after > D> >> the holidays. > D> >> > D> >> -- > D> >> Gleb Smirnoff > D> > > D> > > D>