From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Hamza Mahfooz <hamzamahfooz@linux.microsoft.com>
Cc: Phil Sutter <phil@nwl.cc>,
Jozsef Kadlecsik <kadlec@netfilter.org>,
Florian Westphal <fw@strlen.de>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
coreteam@netfilter.org, linux-kernel@vger.kernel.org
Subject: Re: Soft lock-ups caused by iptables
Date: Thu, 20 Nov 2025 00:14:46 +0100 [thread overview]
Message-ID: <aR5PZvdjpvGD2mIS@calendula> (raw)
In-Reply-To: <20251119222940.GA5070@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>
On Wed, Nov 19, 2025 at 02:29:40PM -0800, Hamza Mahfooz wrote:
> On Wed, Nov 19, 2025 at 03:49:57PM +0100, Phil Sutter wrote:
> > Nftables ruleset validation code was refactored in v6.10 with commit
> > cff3bd012a95 ("netfilter: nf_tables: prefer nft_chain_validate"). This
> > is also present in v5.15.184, so in order to estimate whether a bug is
> > "new" or "old", better really use old kernels not recent minor releases
> > of old major ones. :)
>
> FWIW I tried to repro this on v6.6.45 as well and it also suffers from
> this issue.
This example ruleset does not restore, it is missing ipsets.
prev parent reply other threads:[~2025-11-19 23:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 22:17 Soft lock-ups caused by iptables Hamza Mahfooz
2025-11-19 14:49 ` Phil Sutter
2025-11-19 15:58 ` Florian Westphal
2025-11-19 18:12 ` Phil Sutter
2025-11-19 23:10 ` Pablo Neira Ayuso
2025-11-20 9:34 ` Florian Westphal
2025-11-20 11:22 ` Phil Sutter
2025-11-20 20:38 ` Hamza Mahfooz
2025-11-20 20:46 ` Florian Westphal
2025-11-20 21:07 ` Pablo Neira Ayuso
2025-11-21 20:59 ` Hamza Mahfooz
2025-11-20 21:01 ` Pablo Neira Ayuso
2025-11-19 22:29 ` Hamza Mahfooz
2025-11-19 23:14 ` Pablo Neira Ayuso [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aR5PZvdjpvGD2mIS@calendula \
--to=pablo@netfilter.org \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=hamzamahfooz@linux.microsoft.com \
--cc=horms@kernel.org \
--cc=kadlec@netfilter.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=phil@nwl.cc \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).