From: patchwork-bot+netdevbpf@kernel.org
To: Maoyi Xie <maoyixie.tju@gmail.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, dsahern@kernel.org, kuznet@ms2.inr.ac.ru,
willemb@google.com, willemdebruijn.kernel@gmail.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, maoyi.xie@ntu.edu.sg
Subject: Re: [PATCH net v8 0/2] ipv6: flowlabel: per-netns budget for unprivileged callers
Date: Fri, 08 May 2026 22:10:09 +0000 [thread overview]
Message-ID: <177827820980.868876.13043664849343604381.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260506082416.2259567-1-maoyixie.tju@gmail.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 6 May 2026 16:24:14 +0800 you wrote:
> From: Maoyi Xie <maoyi.xie@ntu.edu.sg>
>
> This series fixes the cross-tenant DoS in net/ipv6/ip6_flowlabel.c.
> v1 through v6 were single-patch postings, each in its own thread.
> v6 review pointed out that the existing fl_size read in
> mem_check() and the corresponding write in fl_intern() are not in
> the same critical section. v7 split the work into 2 patches.
>
> [...]
Here is the summary with links:
- [net,v8,1/2] ipv6: flowlabel: take ip6_fl_lock across mem_check and fl_intern
https://git.kernel.org/netdev/net/c/7ce5556f255a
- [net,v8,2/2] ipv6: flowlabel: enforce per-netns limit for unprivileged callers
https://git.kernel.org/netdev/net/c/e68eadffb724
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-05-08 22:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 8:24 [PATCH net v8 0/2] ipv6: flowlabel: per-netns budget for unprivileged callers Maoyi Xie
2026-05-06 8:24 ` [PATCH net v8 1/2] ipv6: flowlabel: take ip6_fl_lock across mem_check and fl_intern Maoyi Xie
2026-05-06 8:24 ` [PATCH net v8 2/2] ipv6: flowlabel: enforce per-netns limit for unprivileged callers Maoyi Xie
2026-05-08 22:10 ` patchwork-bot+netdevbpf [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=177827820980.868876.13043664849343604381.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=maoyi.xie@ntu.edu.sg \
--cc=maoyixie.tju@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=willemb@google.com \
--cc=willemdebruijn.kernel@gmail.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