From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Pablo Neira Ayuso <pablo@netfilter.org>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH -stable,6.6 v2 1/2] netfilter: nf_tables: bail out if stateful expression provides no .clone
Date: Wed, 19 Mar 2025 06:54:14 -0400 [thread overview]
Message-ID: <20250319055305-bc6e87b8ae7280b1@stable.kernel.org> (raw)
In-Reply-To: <20250318221522.225942-2-pablo@netfilter.org>
[ Sasha's backport helper bot ]
Hi,
The upstream commit SHA1 provided is correct: 3c13725f43dcf43ad8a9bcd6a9f12add19a8f93e
Status in newer kernel trees:
6.13.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
Note: The patch differs from the upstream commit:
---
1: 3c13725f43dcf ! 1: 297e4b7613a98 netfilter: nf_tables: bail out if stateful expression provides no .clone
@@ Metadata
## Commit message ##
netfilter: nf_tables: bail out if stateful expression provides no .clone
+ commit 3c13725f43dcf43ad8a9bcd6a9f12add19a8f93e upstream.
+
All existing NFT_EXPR_STATEFUL provide a .clone interface, remove
fallback to copy content of stateful expression since this is never
exercised and bail out if .clone interface is not defined.
+ Stable-dep-of: fa23e0d4b756 ("netfilter: nf_tables: allow clone callbacks to sleep")
Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
## net/netfilter/nf_tables_api.c ##
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| Current branch | Success | Success |
next prev parent reply other threads:[~2025-03-19 10:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 22:15 [PATCH -stable,6.6 v2 0/2] Netfilter fixes for -stable Pablo Neira Ayuso
2025-03-18 22:15 ` [PATCH -stable,6.6 v2 1/2] netfilter: nf_tables: bail out if stateful expression provides no .clone Pablo Neira Ayuso
2025-03-19 10:54 ` Sasha Levin [this message]
2025-03-18 22:15 ` [PATCH -stable,6.6 v2 2/2] netfilter: nf_tables: allow clone callbacks to sleep Pablo Neira Ayuso
2025-03-19 10:54 ` Sasha Levin
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=20250319055305-bc6e87b8ae7280b1@stable.kernel.org \
--to=sashal@kernel.org \
--cc=pablo@netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.