From nobody Wed Dec 31 18:00:40 2025 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 4dhHn81V3jz6M1l5 for ; Wed, 31 Dec 2025 18:00:44 +0000 (UTC) (envelope-from glebius@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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 (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R12" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4dhHn80hnJz4Ctw; Wed, 31 Dec 2025 18:00:44 +0000 (UTC) (envelope-from glebius@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1767204044; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=aKGcwhjsZDr0PZAxfEcVOQytvvIRVCqHygDszakRdrQ=; b=g4U/dP1g97MWoSab3s+qS2CRWRCpuRpumiKwpil3/U5+aouGefvq9/EMLv4qdo3LBMhVdZ v6Vf2d5yTT6nwG68hR2O3StnXqnJi+BDlzDBcbH08P4o0KIkPReXZcDnlONUzVDyWSC0eV 6iu1nXTiMe8OwS8QXOMt3GM4Qy9AJEc/58/rSfCMfx42j4aMhbk7XL4nCVCQYL+yRqDVfH 2Uqei5b602vv4gTmDQyZTtt7XBQU6OAGREbgUXnQbJ7kNUr24c3d6lH8ytZ83I45jTqf0M BZU50hQRABeSg00UXkyuRFeDhD1y5BM9JtMKFH+xS3M+KRzTYUOrnRteMymeEA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1767204044; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=aKGcwhjsZDr0PZAxfEcVOQytvvIRVCqHygDszakRdrQ=; b=EatLqEgdoIDuyim7mLqnAqaRu9sE75KYi6yeSsCXo7c7ltOIrWspB7maEiLpP1wY/Iu7na HujSIKLURpfZ8uPrj0edkvOlZJVqekS7EG5sGBuW6U98/c6g3FbMi56GtmD7WP2E5phq7j iyh4QuEWCngBBmAJwrlxlohORXqYlzoYhH4t65L7IZhicJL5RFgjMxSnPotpotz355QBMR An130yMd6cUQFRSUUnMKY5TjlynN/7emS9MJU5yV9wO+o9ad6q+V5vbBxcyH3v5Qg6wRUZ 6W5/qqRxBkbbUCZs6WCUSYYLs4r2Ezz4LVhlx9D1vqluUsGKw0W/pL9vZC+AMw== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1767204044; a=rsa-sha256; cv=none; b=PFebQava+onL0ctAUBTgch04ghFxGjDDsbf5e65iTJyKHfwoPhlIzGL3g1+fY89uy6mMFp DmsisFnPzKKaJ9JLoQdjTQzctmX0sP9zWYht/gG4utDXk4ThuDLezmnLl+4qla+jKxssAA IqORKLRmxuUz3WTWg9PM08zWLnMlNY6o1EwGS6FZB/10zRzphR9EsXYJZaEGk+n+pbUSEW S89yhBOTy0FE/VigfFYmJ8DeNPCFaPHJVLfKlrPWDOyOTvQCzfSZezfU/sI9P4Zifu5QVT zWrSPBU0q3JQGx9BVSh2GDLqYM6W5iV7cs7sXnv8UHGRhVlQ4iucHRvUQrRdpw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none Received: from cell.glebi.us (glebi.us [162.251.186.162]) (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 did not present a certificate) (Authenticated sender: glebius) by smtp.freebsd.org (Postfix) with ESMTPSA id 4dhHn72cFJzlvn; Wed, 31 Dec 2025 18:00:43 +0000 (UTC) (envelope-from glebius@freebsd.org) Date: Wed, 31 Dec 2025 10:00:40 -0800 From: Gleb Smirnoff To: Alastair Hogge Cc: "Dan Mahoney (ports)" , FreeBSD User , Ronald Klop , FreeBSD CURRENT Subject: Re: CURRENT: kernel panic in IPFW while stopping jails Message-ID: References: <6ed6434fce515fb9dab694bb649da95b@riseup.net> 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 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6ed6434fce515fb9dab694bb649da95b@riseup.net> 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