From: Pablo Neira Ayuso <pablo@netfilter.org>
To: netfilter-devel@vger.kernel.org
Cc: sashal@kernel.org, gregkh@linuxfoundation.org, stable@vger.kernel.org
Subject: Re: [PATCH -stable,5.10,v2 00/11] stable fixes for 5.10
Date: Wed, 5 Jul 2023 17:15:24 +0200 [thread overview]
Message-ID: <ZKWJDBS4w5Wc9uho@calendula> (raw)
In-Reply-To: <20230705150011.59408-1-pablo@netfilter.org>
Hi,
On Wed, Jul 05, 2023 at 05:00:00PM +0200, Pablo Neira Ayuso wrote:
> Hi Greg, Sasha,
>
> [ This is v2 appends patch #11 f838e0906dd3 as Florian suggested. ]
^^^^^^^^^^^^
this should be 2024439bd5ce instead
> The following list shows the backported patches, I am using original
> commit IDs for reference:
>
> 1) 0854db2aaef3 ("netfilter: nf_tables: use net_generic infra for transaction data")
>
> 2) 81ea01066741 ("netfilter: nf_tables: add rescheduling points during loop detection walks")
>
> 3) 1240eb93f061 ("netfilter: nf_tables: incorrect error path handling with NFT_MSG_NEWRULE")
>
> 4) 4bedf9eee016 ("netfilter: nf_tables: fix chain binding transaction logic")
>
> 5) 26b5a5712eb8 ("netfilter: nf_tables: add NFT_TRANS_PREPARE_ERROR to deal with bound set/chain")
>
> 6) 938154b93be8 ("netfilter: nf_tables: reject unbound anonymous set before commit phase")
>
> 7) 62e1e94b246e ("netfilter: nf_tables: reject unbound chain set before commit phase")
>
> 8) f8bb7889af58 ("netfilter: nftables: rename set element data activation/deactivation functions")
>
> 9) 628bd3e49cba ("netfilter: nf_tables: drop map element references from preparation phase")
>
> 10) 3e70489721b6 ("netfilter: nf_tables: unbind non-anonymous set if rule construction fails")
>
> 11) f838e0906dd3 ("netfilter: nf_tables: fix scheduling-while-atomic splat")
Nitpick, incorrect original commit in this cover letter patch #11:
11) 2024439bd5ce ("netfilter: nf_tables: fix scheduling-while-atomic splat")
Backport of patch #11 already points to the valid original commit.
> Note:
>
> - Patch #1 is a backported dependency patch required by these fixes.
> - Patch #2 needs a follow up fix coming in this series as patch #11.
>
> Please, apply,
> Thanks.
>
> Florian Westphal (3):
> netfilter: nf_tables: use net_generic infra for transaction data
> netfilter: nf_tables: add rescheduling points during loop detection walks
> netfilter: nf_tables: fix scheduling-while-atomic splat
>
> Pablo Neira Ayuso (8):
> netfilter: nf_tables: incorrect error path handling with NFT_MSG_NEWRULE
> netfilter: nf_tables: fix chain binding transaction logic
> netfilter: nf_tables: add NFT_TRANS_PREPARE_ERROR to deal with bound set/chain
> netfilter: nf_tables: reject unbound anonymous set before commit phase
> netfilter: nf_tables: reject unbound chain set before commit phase
> netfilter: nftables: rename set element data activation/deactivation functions
> netfilter: nf_tables: drop map element references from preparation phase
> netfilter: nf_tables: unbind non-anonymous set if rule construction fails
>
> include/net/netfilter/nf_tables.h | 41 +-
> include/net/netns/nftables.h | 7 -
> net/netfilter/nf_tables_api.c | 692 +++++++++++++++++++++---------
> net/netfilter/nf_tables_offload.c | 30 +-
> net/netfilter/nft_chain_filter.c | 11 +-
> net/netfilter/nft_dynset.c | 6 +-
> net/netfilter/nft_immediate.c | 90 +++-
> net/netfilter/nft_set_bitmap.c | 5 +-
> net/netfilter/nft_set_hash.c | 23 +-
> net/netfilter/nft_set_pipapo.c | 14 +-
> net/netfilter/nft_set_rbtree.c | 5 +-
> 11 files changed, 678 insertions(+), 246 deletions(-)
>
> --
> 2.30.2
>
prev parent reply other threads:[~2023-07-05 15:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 15:00 [PATCH -stable,5.10,v2 00/11] stable fixes for 5.10 Pablo Neira Ayuso
2023-07-05 15:00 ` [PATCH -stable,5.10,v2 01/11] netfilter: nf_tables: use net_generic infra for transaction data Pablo Neira Ayuso
2023-07-12 6:06 ` Salvatore Bonaccorso
2023-07-12 8:19 ` Pablo Neira Ayuso
2023-07-05 15:00 ` [PATCH -stable,5.10,v2 02/11] netfilter: nf_tables: add rescheduling points during loop detection walks Pablo Neira Ayuso
2023-07-05 15:00 ` [PATCH -stable,5.10,v2 03/11] netfilter: nf_tables: incorrect error path handling with NFT_MSG_NEWRULE Pablo Neira Ayuso
2023-07-05 15:00 ` [PATCH -stable,5.10,v2 04/11] netfilter: nf_tables: fix chain binding transaction logic Pablo Neira Ayuso
2023-07-05 15:00 ` [PATCH -stable,5.10,v2 05/11] netfilter: nf_tables: add NFT_TRANS_PREPARE_ERROR to deal with bound set/chain Pablo Neira Ayuso
2023-07-05 15:00 ` [PATCH -stable,5.10,v2 06/11] netfilter: nf_tables: reject unbound anonymous set before commit phase Pablo Neira Ayuso
2023-07-05 15:00 ` [PATCH -stable,5.10,v2 07/11] netfilter: nf_tables: reject unbound chain " Pablo Neira Ayuso
2023-07-05 15:00 ` [PATCH -stable,5.10,v2 08/11] netfilter: nftables: rename set element data activation/deactivation functions Pablo Neira Ayuso
2023-07-05 15:00 ` [PATCH -stable,5.10,v2 09/11] netfilter: nf_tables: drop map element references from preparation phase Pablo Neira Ayuso
2023-07-05 15:00 ` [PATCH -stable,5.10,v2 10/11] netfilter: nf_tables: unbind non-anonymous set if rule construction fails Pablo Neira Ayuso
2023-07-05 15:00 ` [PATCH -stable,5.10,v2 11/11] netfilter: nf_tables: fix scheduling-while-atomic splat Pablo Neira Ayuso
2023-07-05 15:15 ` 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=ZKWJDBS4w5Wc9uho@calendula \
--to=pablo@netfilter.org \
--cc=gregkh@linuxfoundation.org \
--cc=netfilter-devel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).