From: patchwork-bot+netdevbpf@kernel.org
To: Nuoqi Gui <gnq25@mails.tsinghua.edu.cn>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, john.fastabend@gmail.com, eddyz87@gmail.com,
memxor@gmail.com, yonghong.song@linux.dev, shuah@kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH bpf-next 0/2] bpf: Enforce BTF pointer write checks for global args
Date: Tue, 09 Jun 2026 16:01:30 +0000 [thread overview]
Message-ID: <178102089039.2105069.12169119537576635643.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260609-f01-04-btf-writable-arg-v1-0-f449cd970669@mails.tsinghua.edu.cn>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:
On Tue, 09 Jun 2026 22:43:49 +0800 you wrote:
> check_mem_reg() verifies both read and write access when a caller passes
> memory into a global subprogram. For PTR_TO_BTF_ID callers,
> check_helper_mem_access() currently always checks the access as BPF_READ.
>
> That lets a tracing program pass a task_struct field pointer to a global
> subprogram argument typed as writable memory. The direct field store is rejected
> with "only read is supported", but the callee is validated with a generic
> writable PTR_TO_MEM argument and can store through it.
>
> [...]
Here is the summary with links:
- [bpf-next,1/2] bpf: Enforce write checks for BTF pointer helper access
https://git.kernel.org/bpf/bpf-next/c/fa75b7c85b0d
- [bpf-next,2/2] selftests/bpf: Cover writable BTF field global subprog args
https://git.kernel.org/bpf/bpf-next/c/af8c3f170f73
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-06-09 16:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 14:43 [PATCH bpf-next 0/2] bpf: Enforce BTF pointer write checks for global args Nuoqi Gui
2026-06-09 14:43 ` [PATCH bpf-next 1/2] bpf: Enforce write checks for BTF pointer helper access Nuoqi Gui
2026-06-09 14:43 ` [PATCH bpf-next 2/2] selftests/bpf: Cover writable BTF field global subprog args Nuoqi Gui
2026-06-09 16:01 ` 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=178102089039.2105069.12169119537576635643.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=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=gnq25@mails.tsinghua.edu.cn \
--cc=john.fastabend@gmail.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=memxor@gmail.com \
--cc=shuah@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