From: patchwork-bot+netdevbpf@kernel.org
To: Jiayuan Chen <jiayuan.chen@linux.dev>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
corbet@lwn.net, skhan@linuxfoundation.org, rdunlap@infradead.org,
dsahern@kernel.org, idosch@nvidia.com, tglx@kernel.org,
joel.granados@kernel.org, fmancera@suse.de, petr.pavlu@suse.com,
kuniyu@google.com, willemb@google.com, maoyi.xie@ntu.edu.sg,
oleg@redhat.com, zhanxusheng1024@gmail.com,
gerd.rausch@oracle.com, razor@blackwall.org,
chia-yu.chang@nokia-bell-labs.com, bronzed_45_vested@icloud.com,
hannes@stressinduktion.org, fbl@redhat.com, pmladek@suse.com,
paulmck@kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v3 0/5] net: fix misc signed overflows caused by bad sysctl values
Date: Fri, 06 Nov 2026 12:20:07 +0000 [thread overview]
Message-ID: <179396760723.585103.10973765623205620658.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261101061331.286404-1-jiayuan.chen@linux.dev>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Sun, 1 Nov 2026 14:11:58 +0800 you wrote:
> Recently I have reviewed quite a few fixes for variable overflows caused
> by config values, i.e. a value set from sysctl, module params or netlink
> that is accepted as valid but later overflows when it is used in a
> calculation. I believe there are more of these still out there, so I
> used an LLM to dig through the code and it found the issues fixed in
> this series.
>
> [...]
Here is the summary with links:
- [net,v3,1/5] ipv6: restrict gc_elasticity to 31
https://git.kernel.org/netdev/net-next/c/3ff59dd75d71
- [net,v3,2/5] ipv4: fix shift-out-of-bounds in ip_rt_send_redirect()
https://git.kernel.org/netdev/net-next/c/26627b7bf8cd
- [net,v3,3/5] ipv6: restrict mld_qrv to 255
https://git.kernel.org/netdev/net-next/c/6d6bdc1b943c
- [net,v3,4/5] ipv4: restrict igmp_qrv to 255
https://git.kernel.org/netdev/net-next/c/0bc7b5b2985f
- [net,v3,5/5] net: restrict message_cost and message_burst to non-negative values
https://git.kernel.org/netdev/net-next/c/75f5722df2b4
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-11-06 13:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-01 6:11 Jiayuan Chen
2026-11-01 6:11 ` [PATCH net v3 1/5] ipv6: restrict gc_elasticity to 31 Jiayuan Chen
2026-11-02 1:25 ` Hangbin Liu
2026-11-01 6:12 ` [PATCH net v3 2/5] ipv4: fix shift-out-of-bounds in ip_rt_send_redirect() Jiayuan Chen
2026-11-03 5:28 ` Kuniyuki Iwashima
2026-11-01 6:12 ` [PATCH net v3 3/5] ipv6: restrict mld_qrv to 255 Jiayuan Chen
2026-11-01 10:23 ` Nikolay Aleksandrov
2026-11-02 1:31 ` Hangbin Liu
2026-11-03 5:29 ` Kuniyuki Iwashima
2026-11-01 6:12 ` [PATCH net v3 4/5] ipv4: restrict igmp_qrv " Jiayuan Chen
2026-11-02 1:29 ` Hangbin Liu
2026-11-03 5:29 ` Kuniyuki Iwashima
2026-11-01 6:12 ` [PATCH net v3 5/5] net: restrict message_cost and message_burst to non-negative values Jiayuan Chen
2026-11-02 1:55 ` Hangbin Liu
2026-11-02 2:23 ` Jiayuan Chen
2026-11-02 3:32 ` Hangbin Liu
2026-11-03 5:30 ` Kuniyuki Iwashima
2026-11-05 11:05 ` [PATCH net v3 0/5] net: fix misc signed overflows caused by bad sysctl values Paolo Abeni
2026-11-06 12:20 ` 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=179396760723.585103.10973765623205620658.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bronzed_45_vested@icloud.com \
--cc=chia-yu.chang@nokia-bell-labs.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@kernel.org \
--cc=fbl@redhat.com \
--cc=fmancera@suse.de \
--cc=gerd.rausch@oracle.com \
--cc=hannes@stressinduktion.org \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=jiayuan.chen@linux.dev \
--cc=joel.granados@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maoyi.xie@ntu.edu.sg \
--cc=netdev@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=pabeni@redhat.com \
--cc=paulmck@kernel.org \
--cc=petr.pavlu@suse.com \
--cc=pmladek@suse.com \
--cc=razor@blackwall.org \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--cc=tglx@kernel.org \
--cc=willemb@google.com \
--cc=zhanxusheng1024@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
all inboxes | Powered by JetHome®