From: Florian Westphal <fw@strlen.de>
To: Sasha Levin <sashal@kernel.org>
Cc: patches@lists.linux.dev, stable@vger.kernel.org,
Hamza Mahfooz <hamzamahfooz@linux.microsoft.com>,
pablo@netfilter.org, netfilter-devel@vger.kernel.org,
coreteam@netfilter.org
Subject: Re: [PATCH AUTOSEL 6.18-6.6] netfilter: nf_tables: avoid chain re-validation if possible
Date: Tue, 23 Dec 2025 11:12:23 +0100 [thread overview]
Message-ID: <aUprB84-pTouDuac@strlen.de> (raw)
In-Reply-To: <20251223100518.2383364-2-sashal@kernel.org>
Sasha Levin <sashal@kernel.org> wrote:
> + if (WARN_ON_ONCE(!nft_is_base_chain(ctx->chain)))
> + return false;
This WARN will fire unless you also pick up
a67fd55f6a09 ("netfilter: nf_tables: remove redundant chain validation on register store")
Alternatively, drop the WARN: "if (!nft_is_base_chain...".
prev parent reply other threads:[~2025-12-23 10:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251223100518.2383364-1-sashal@kernel.org>
2025-12-23 10:05 ` [PATCH AUTOSEL 6.18-6.6] netfilter: nf_tables: avoid chain re-validation if possible Sasha Levin
2025-12-23 10:12 ` Florian Westphal [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=aUprB84-pTouDuac@strlen.de \
--to=fw@strlen.de \
--cc=coreteam@netfilter.org \
--cc=hamzamahfooz@linux.microsoft.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=patches@lists.linux.dev \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
/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).