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, fw@strlen.de
Subject: Re: [PATCH net 0/4] Netfilter fixes for net
Date: Thu, 28 Nov 2024 13:33:19 +0100 [thread overview]
Message-ID: <Z0hjDyQq-tRrMsHy@calendula> (raw)
In-Reply-To: <20241128122305.14091-1-pablo@netfilter.org>
Hi,
On Thu, Nov 28, 2024 at 01:23:01PM +0100, Pablo Neira Ayuso wrote:
> Hi,
>
> The following patchset contains Netfilter fixes for net:
>
> 1) Fix esoteric UB due to uninitialized stack access in ip_vs_protocol_init(),
> from Jinghao Jia.
>
> 2) Fix iptables xt_LED slab-out-of-bounds, reported by syzbot,
> patch from Dmitry Antipov.
>
> 3) Remove WARN_ON_ONCE reachable from userspace to cap maximum cgroup
> levels to 255, reported by syzbot.
>
> 4) Fix nft_inner incorrect use of percpu area to store tunnel parser
> context with softirqs, reported by syzbot.
This patch #4 is missing Fixes: tag. Apologies.
I am going to prepare another batch and resubmit.
next prev parent reply other threads:[~2024-11-28 12:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-28 12:23 [PATCH net 0/4] Netfilter fixes for net Pablo Neira Ayuso
2024-11-28 12:23 ` [PATCH net 1/4] ipvs: fix UB due to uninitialized stack access in ip_vs_protocol_init() Pablo Neira Ayuso
2024-11-28 12:23 ` [PATCH net 2/4] netfilter: x_tables: fix LED ID check in led_tg_check() Pablo Neira Ayuso
2024-11-28 12:23 ` [PATCH net 3/4] netfilter: nft_socket: remove WARN_ON_ONCE on maximum cgroup level Pablo Neira Ayuso
2024-11-28 12:23 ` [PATCH net 4/4] netfilter: nft_inner: incorrect percpu area handling under softirq Pablo Neira Ayuso
2024-11-28 12:33 ` Pablo Neira Ayuso [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-31 10:01 [PATCH net 0/4] Netfilter fixes for net Pablo Neira Ayuso
2024-10-31 11:20 ` patchwork-bot+netdevbpf
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=Z0hjDyQq-tRrMsHy@calendula \
--to=pablo@netfilter.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--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