From: Greg KH <gregkh@linuxfoundation.org>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org, stable@vger.kernel.org,
sashal@kernel.org
Subject: Re: [PATCH -stable,5.10 v3 01/11] netfilter: nf_tables: use net_generic infra for transaction data
Date: Sun, 16 Jul 2023 21:18:29 +0200 [thread overview]
Message-ID: <2023071608-pushcart-egotism-c77f@gregkh> (raw)
In-Reply-To: <20230713084859.71541-2-pablo@netfilter.org>
On Thu, Jul 13, 2023 at 10:48:49AM +0200, Pablo Neira Ayuso wrote:
> From: Florian Westphal <fw@strlen.de>
>
> [ Upstream commit 0854db2aaef3fcdd3498a9d299c60adea2aa3dc6 ]
>
> This moves all nf_tables pernet data from struct net to a net_generic
> extension, with the exception of the gencursor.
>
> The latter is used in the data path and also outside of the nf_tables
> core. All others are only used from the configuration plane.
>
> Signed-off-by: Florian Westphal <fw@strlen.de>
> Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
> ---
> include/net/netfilter/nf_tables.h | 10 +
> include/net/netns/nftables.h | 7 -
> net/netfilter/nf_tables_api.c | 382 ++++++++++++++++++------------
> net/netfilter/nf_tables_offload.c | 30 ++-
> net/netfilter/nft_chain_filter.c | 11 +-
> net/netfilter/nft_dynset.c | 6 +-
> 6 files changed, 279 insertions(+), 167 deletions(-)
This doesn't apply to the 5.10.y tree, what version did you make it
against?
thanks,
greg k-h
next prev parent reply other threads:[~2023-07-16 19:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 8:48 [PATCH -stable,5.10 v3 00/11] Netfilter stable fixes for 5.10 Pablo Neira Ayuso
2023-07-13 8:48 ` [PATCH -stable,5.10 v3 01/11] netfilter: nf_tables: use net_generic infra for transaction data Pablo Neira Ayuso
2023-07-16 19:18 ` Greg KH [this message]
2023-07-16 19:19 ` Greg KH
2023-07-13 8:48 ` [PATCH -stable,5.10 v3 02/11] netfilter: nf_tables: add rescheduling points during loop detection walks Pablo Neira Ayuso
2023-07-13 8:48 ` [PATCH -stable,5.10 v3 03/11] netfilter: nf_tables: incorrect error path handling with NFT_MSG_NEWRULE Pablo Neira Ayuso
2023-07-13 8:48 ` [PATCH -stable,5.10 v3 04/11] netfilter: nf_tables: fix chain binding transaction logic Pablo Neira Ayuso
2023-07-13 8:48 ` [PATCH -stable,5.10 v3 05/11] netfilter: nf_tables: add NFT_TRANS_PREPARE_ERROR to deal with bound set/chain Pablo Neira Ayuso
2023-07-13 8:48 ` [PATCH -stable,5.10 v3 06/11] netfilter: nf_tables: reject unbound anonymous set before commit phase Pablo Neira Ayuso
2023-07-13 8:48 ` [PATCH -stable,5.10 v3 07/11] netfilter: nf_tables: reject unbound chain " Pablo Neira Ayuso
2023-07-13 8:48 ` [PATCH -stable,5.10 v3 08/11] netfilter: nftables: rename set element data activation/deactivation functions Pablo Neira Ayuso
2023-07-13 8:48 ` [PATCH -stable,5.10 v3 09/11] netfilter: nf_tables: drop map element references from preparation phase Pablo Neira Ayuso
2023-07-13 8:48 ` [PATCH -stable,5.10 v3 10/11] netfilter: nf_tables: unbind non-anonymous set if rule construction fails Pablo Neira Ayuso
2023-07-13 8:48 ` [PATCH -stable,5.10 v3 11/11] netfilter: nf_tables: fix scheduling-while-atomic splat Pablo Neira Ayuso
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=2023071608-pushcart-egotism-c77f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--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