From: patchwork-bot+netdevbpf@kernel.org
To: Zhao Gongyi <zhaogongyi@bytedance.com>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, john.fastabend@gmail.com,
jakub@cloudflare.com, jiayuan.chen@linux.dev,
edumazet@google.com, kuniyu@google.com, pabeni@redhat.com,
willemb@google.com, davem@davemloft.net, kuba@kernel.org,
horms@kernel.org, daniel@iogearbox.net, zhaogongyi@BYTEDANCE.COM
Subject: Re: [PATCH bpf v2] bpf, sockmap: reject max_entries > INT_MAX in sock_map_alloc
Date: Wed, 23 Sep 2026 00:00:05 +0000 [thread overview]
Message-ID: <179012160516.137376.9044341582800034905.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260917121016.48171-1-zhaogongyi@bytedance.com>
Hello:
This patch was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 17 Sep 2026 20:10:16 +0800 you wrote:
> From: Zhao Gongyi <zhaogongyi@BYTEDANCE.COM>
>
> sock_map_alloc() only rejects max_entries == 0 and otherwise allows any
> u32 value. sock_map_free() then walks the sks[] array with a signed int
> iterator:
>
> int i;
> for (i = 0; i < stab->map.max_entries; i++)
> struct sock **psk = &stab->sks[i];
>
> [...]
Here is the summary with links:
- [bpf,v2] bpf, sockmap: reject max_entries > INT_MAX in sock_map_alloc
https://git.kernel.org/bpf/bpf/c/814a81c842bd
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-09-23 0:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 7:17 [PATCH bpf] bpf, sockmap: reject max_entries > INT_MAX in sock_map_alloc Zhao Gongyi
2026-09-15 8:13 ` bot+bpf-ci
2026-09-22 17:06 ` John Fastabend
2026-09-17 12:10 ` [PATCH bpf v2] " Zhao Gongyi
2026-09-23 0:00 ` 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=179012160516.137376.9044341582800034905.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jakub@cloudflare.com \
--cc=jiayuan.chen@linux.dev \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.com \
--cc=zhaogongyi@bytedance.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.