From nobody Sun Dec 28 09:28:51 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 4dfDZ16yP1z6LVtk for ; Sun, 28 Dec 2025 09:28:57 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward500d.mail.yandex.net (forward500d.mail.yandex.net [178.154.239.208]) (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) by mx1.freebsd.org (Postfix) with ESMTPS id 4dfDYz661pz3bCx for ; Sun, 28 Dec 2025 09:28:55 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yandex.ru header.s=mail header.b=HVzXvJwZ; dmarc=pass (policy=none) header.from=yandex.ru; spf=pass (mx1.freebsd.org: domain of bu7cher@yandex.ru designates 178.154.239.208 as permitted sender) smtp.mailfrom=bu7cher@yandex.ru Received: from mail-nwsmtp-mxback-production-main-82.klg.yp-c.yandex.net (mail-nwsmtp-mxback-production-main-82.klg.yp-c.yandex.net [IPv6:2a02:6b8:c43:a2b:0:640:585f:0]) by forward500d.mail.yandex.net (Yandex) with ESMTPS id 4A87080612; Sun, 28 Dec 2025 12:28:53 +0300 (MSK) Received: from mail.yandex.ru (2a02:6b8:c43:4901:0:640:35d8:0 [2a02:6b8:c43:4901:0:640:35d8:0]) by mail-nwsmtp-mxback-production-main-82.klg.yp-c.yandex.net (mxback/Yandex) with HTTPS id TScCfg1smGk0-u5zjXEN1; Sun, 28 Dec 2025 12:28:52 +0300 X-Yandex-Fwd: 1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1766914132; bh=Px1JFDUdSEycftreStgnIrQAaIq9JrQ495xj6TZ7bTY=; h=Message-Id:References:Date:Cc:Subject:In-Reply-To:To:From; b=HVzXvJwZF6K4pJcf4bp3df8gzWESTOaUwv3+phpE+SCVcE9GIZXl0nRB0RgelgwFG qcvSW0bDKDVPs9QK4E+1aFqkJOyyNitRtvbNtP9lywWRjgqZ7ZRuT4eZ+fwfgbEj7m /rmuZwn8AtVBYfmBMRCpVgyd9a3Wokn8RSPZmu48= Received: by mail-sendbernar-production-main-69.klg.yp-c.yandex.net (sendbernar/Yandex) with HTTPS id 636bbd152db75e65dacb6607979126e1; Sun, 28 Dec 2025 12:28:51 +0300 From: Andrey V. Elsukov To: FreeBSD User , Ronald Klop Cc: FreeBSD CURRENT , David Wolfskill In-Reply-To: <20251225190836.6769e6d6@hermann> References: <20251225170828.7aef61df@hermann> <902742484.3865.1766683845222@localhost> <20251225190836.6769e6d6@hermann> Subject: Re: CURRENT: kernel panic in IPFW while stopping jails 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 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Sun, 28 Dec 2025 12:28:51 +0300 Message-Id: <26521766914006@mail.yandex.ru> Content-Transfer-Encoding: 8bit Content-Type: text/html; charset=utf-8 X-Spamd-Bar: - X-Spamd-Result: default: False [-1.63 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_SPAM_MEDIUM(0.97)[0.967]; NEURAL_HAM_SHORT(-0.90)[-0.901]; DMARC_POLICY_ALLOW(-0.50)[yandex.ru,none]; R_DKIM_ALLOW(-0.20)[yandex.ru:s=mail]; R_SPF_ALLOW(-0.20)[+ip4:178.154.239.208/28]; MIME_HTML_ONLY(0.20)[]; FREEMAIL_ENVFROM(0.00)[yandex.ru]; ARC_NA(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2a02:6b8:c43:4901:0:640:35d8:0:received]; FREEMAIL_FROM(0.00)[yandex.ru]; MIME_TRACE(0.00)[0:~]; MLMMJ_DEST(0.00)[freebsd-current@freebsd.org]; MID_RHS_MATCH_FROMTLD(0.00)[]; RCVD_TLS_ALL(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; TO_MATCH_ENVRCPT_SOME(0.00)[]; TO_DN_ALL(0.00)[]; DWL_DNSWL_NONE(0.00)[yandex.ru:dkim]; RCVD_COUNT_THREE(0.00)[3]; DKIM_TRACE(0.00)[yandex.ru:+] X-Rspamd-Queue-Id: 4dfDYz661pz3bCx

On Thu, 25 Dec 2025 18:30:45 +0100 (CET)
Ronald Klop <ronald-lists@klop.ws> wrote:
 

 Do you use bpf or tap in your ipfw rules?
 A panic with that was mentioned on the 20th. And fixed in the mean time of I
 remember correctly. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=291854
 Regards,Ronald


Indeed, all boxes in question do have a tap0 at least defined -but in only one
case used.

Hi,
 
I don't think it is related to tap0.
If it is related to recent BPF changes in ipfw, you can try to remove "log" opcode
from your rules.
 
-- 
WBR, Andrey V. Elsukov