From: patchwork-bot+netdevbpf@kernel.org
To: Yiyang Chen <chenyy23@mails.tsinghua.edu.cn>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
eddyz87@gmail.com, memxor@gmail.com, john.fastabend@gmail.com,
martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
jolsa@kernel.org, emil@etsalapatis.com, shuah@kernel.org,
bpf@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v3 0/2] bpf: Reject MEM_ALLOC BTF accesses past bounds
Date: Mon, 06 Jul 2026 22:30:10 +0000 [thread overview]
Message-ID: <178337701039.1232545.8737132384800629878.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1782807039.git.chenyy23@mails.tsinghua.edu.cn>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:
On Tue, 30 Jun 2026 08:41:25 +0000 you wrote:
> BTF struct walks can relax the top-level struct-size check for trailing
> flexible arrays. That relaxation must not let a PTR_TO_BTF_ID | MEM_ALLOC
> access escape the bytes allocated by bpf_obj_new() or bpf_percpu_obj_new().
>
> Patch 1 rejects MEM_ALLOC BTF walks whose access range reaches past the
> current struct size before applying the flexible-array relaxation. This now
> also applies to struct ID matching used by kfunc and kptr type checks.
> Patch 2 adds a linked_list negative loader case for this path.
>
> [...]
Here is the summary with links:
- [bpf-next,v3,1/2] bpf: Reject MEM_ALLOC BTF accesses past object bounds
https://git.kernel.org/bpf/bpf-next/c/a642e693cecb
- [bpf-next,v3,2/2] selftests/bpf: Cover MEM_ALLOC access past object bounds
https://git.kernel.org/bpf/bpf-next/c/d17f5823ca8c
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-07-06 22:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 8:41 [PATCH bpf-next v3 0/2] bpf: Reject MEM_ALLOC BTF accesses past bounds Yiyang Chen
2026-06-30 8:41 ` [PATCH bpf-next v3 1/2] bpf: Reject MEM_ALLOC BTF accesses past object bounds Yiyang Chen
2026-07-06 18:53 ` Eduard Zingerman
2026-07-06 21:43 ` Amery Hung
2026-06-30 8:41 ` [PATCH bpf-next v3 2/2] selftests/bpf: Cover MEM_ALLOC access " Yiyang Chen
2026-07-06 22:30 ` 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=178337701039.1232545.8737132384800629878.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=chenyy23@mails.tsinghua.edu.cn \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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