From: Pablo Neira Ayuso <pablo@netfilter.org>
To: netfilter-devel@vger.kernel.org
Cc: davem@davemloft.net, netdev@vger.kernel.org, kuba@kernel.org,
pabeni@redhat.com, edumazet@google.com
Subject: [PATCH net 0/4] Netfilter fixes for net
Date: Wed, 30 Nov 2022 13:19:30 +0100 [thread overview]
Message-ID: <20221130121934.1125-1-pablo@netfilter.org> (raw)
Hi,
The following patchset contains Netfilter fixes for net:
1) Check for interval validity in all concatenation fields in
nft_set_pipapo, from Stefano Brivio.
2) Missing preemption disabled in conntrack and flowtable stat
updates, from Xin Long.
3) Fix compilation warning when CONFIG_NF_CONNTRACK_MARK=n.
Except for 3) which was a bug introduced in a recent fix in 6.1-rc.
Anything else, broken for several releases.
Please, pull these changes from:
git://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf.git
Thanks.
----------------------------------------------------------------
The following changes since commit f2fc2280faabafc8df83ee007699d21f7a6301fe:
Merge branch 'wwan-iosm-fixes' (2022-11-28 11:31:59 +0000)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf.git HEAD
for you to fetch changes up to 1feeae071507ad65cf9f462a1bdd543a4bf89e71:
netfilter: ctnetlink: fix compilation warning after data race fixes in ct mark (2022-11-30 13:08:49 +0100)
----------------------------------------------------------------
Pablo Neira Ayuso (1):
netfilter: ctnetlink: fix compilation warning after data race fixes in ct mark
Stefano Brivio (1):
netfilter: nft_set_pipapo: Actually validate intervals in fields after the first one
Xin Long (2):
netfilter: flowtable_offload: fix using __this_cpu_add in preemptible
netfilter: conntrack: fix using __this_cpu_add in preemptible
net/netfilter/nf_conntrack_core.c | 6 +++---
net/netfilter/nf_conntrack_netlink.c | 19 ++++++++++---------
net/netfilter/nf_flow_table_offload.c | 6 +++---
net/netfilter/nft_set_pipapo.c | 5 +++--
4 files changed, 19 insertions(+), 17 deletions(-)
next reply other threads:[~2022-11-30 12:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-30 12:19 Pablo Neira Ayuso [this message]
2022-11-30 12:19 ` [PATCH net 1/4] netfilter: nft_set_pipapo: Actually validate intervals in fields after the first one Pablo Neira Ayuso
2022-12-01 6:10 ` patchwork-bot+netdevbpf
2022-11-30 12:19 ` [PATCH net 2/4] netfilter: flowtable_offload: fix using __this_cpu_add in preemptible Pablo Neira Ayuso
2022-11-30 12:19 ` [PATCH net 3/4] netfilter: conntrack: " Pablo Neira Ayuso
2022-11-30 12:19 ` [PATCH net 4/4] netfilter: ctnetlink: fix compilation warning after data race fixes in ct mark Pablo Neira Ayuso
-- strict thread matches above, loose matches on Subject: below --
2024-03-28 3:18 [PATCH net 0/4] Netfilter fixes for net Pablo Neira Ayuso
2023-03-09 17:46 Pablo Neira Ayuso
2023-03-10 11:08 ` Jeremy Sowden
2023-03-10 11:44 ` Pablo Neira Ayuso
2023-01-24 18:39 Pablo Neira Ayuso
2022-05-27 9:20 Pablo Neira Ayuso
2022-04-25 9:16 Pablo Neira Ayuso
2022-01-06 21:51 Pablo Neira Ayuso
2021-02-05 0:17 Pablo Neira Ayuso
2020-12-18 12:04 Pablo Neira Ayuso
2020-12-09 22:18 Pablo Neira Ayuso
2020-12-10 2:59 ` David Miller
2020-11-21 12:35 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=20221130121934.1125-1-pablo@netfilter.org \
--to=pablo@netfilter.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.com \
/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).