From: patchwork-bot+netdevbpf@kernel.org
To: Yiyang Chen <chenyy23@mails.tsinghua.edu.cn>
Cc: ast@kernel.org, daniel@iogearbox.net, john.fastabend@gmail.com,
andrii@kernel.org, eddyz87@gmail.com, memxor@gmail.com,
martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
jolsa@kernel.org, emil@etsalapatis.com, ihor.solodrai@linux.dev,
shuah@kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
ameryhung@gmail.com, listout@listout.xyz
Subject: Re: [PATCH bpf-next v4 0/2] bpf: Enforce trusted BTF ID argument provenance
Date: Mon, 19 Oct 2026 02:10:06 +0000 [thread overview]
Message-ID: <179237580653.2359447.8270002565749496312.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261007-a3-arg-trusted-v4-v4-0-253ef3a1a69a@mails.tsinghua.edu.cn>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:
On Wed, 07 Oct 2026 16:25:28 +0000 you wrote:
> A global subprogram parameter tagged __arg_trusted is verified with
> PTR_TRUSTED, but its call-site type check also accepts bare PTR_TO_BTF_ID and
> MEM_RCU registers. This lets a callee use a pointer with weaker provenance
> under the trusted-pointer contract, including passing it to a non-KF_RCU
> kfunc.
>
> Encode the trusted-pointer requirement in generated kfunc prototypes and
> drive the shared provenance check from the argument contract. A KF_RCU
> kfunc additionally permits MEM_RCU, while a global __arg_trusted argument
> requires a referenced or trusted pointer. Normalize nullability when the
> argument contract permits it.
>
> [...]
Here is the summary with links:
- [bpf-next,v4,1/2] bpf: Enforce trusted BTF ID argument provenance
https://git.kernel.org/bpf/bpf-next/c/c3a0bfddaee4
- [bpf-next,v4,2/2] selftests/bpf: Cover trusted BTF ID argument provenance
https://git.kernel.org/bpf/bpf-next/c/71b6a960c73f
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-10-19 2:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 16:25 Yiyang Chen
2026-10-07 16:25 ` [PATCH bpf-next v4 1/2] " Yiyang Chen
2026-10-07 22:30 ` Amery Hung
2026-10-07 16:25 ` [PATCH bpf-next v4 2/2] selftests/bpf: Cover " Yiyang Chen
2026-10-07 22:24 ` Amery Hung
2026-10-19 2: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=179237580653.2359447.8270002565749496312.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ameryhung@gmail.com \
--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=ihor.solodrai@linux.dev \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=listout@listout.xyz \
--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
all inboxes | Powered by JetHome®