From: patchwork-bot+netdevbpf@kernel.org
To: Slava Imameev <slava.imameev@crowdstrike.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org,
yonghong.song@linux.dev, john.fastabend@gmail.com,
kpsingh@kernel.org, sdf@fomichev.me, haoluo@google.com,
jolsa@kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
shuah@kernel.org, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org, netdev@vger.kernel.org,
linux-kselftest@vger.kernel.org,
linux-open-source@crowdstrike.com
Subject: Re: [PATCH bpf-next v6 0/2] bpf: Add multi-level pointer parameter support for trampolines
Date: Tue, 24 Mar 2026 20:40:16 +0000 [thread overview]
Message-ID: <177438481628.1297770.15710276152087682651.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260314082127.7939-1-slava.imameev@crowdstrike.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sat, 14 Mar 2026 19:21:25 +1100 you wrote:
> This is v6 of a series adding support for new pointer types for
> trampoline parameters.
>
> Originally, only support for multi-level pointers was proposed.
> As suggested during review, it was extended to single-level pointers.
> During discussion, it was proposed to add support for any single or
> multi-level pointer type that is not a single-level pointer to a
> structure, with the condition if (!btf_type_is_struct(t)). The safety
> of this condition is based on BTF data verification performed for
> modules and programs, and vmlinux BTF being trusted to not contain
> invalid types, so it is not possible for invalid types, like
> PTR->DATASEC, PTR->FUNC, PTR->VAR and corresponding multi-level
> pointers, to reach btf_ctx_access.
>
> [...]
Here is the summary with links:
- [bpf-next,v6,1/2] bpf: Support pointer param types via SCALAR_VALUE for trampolines
https://git.kernel.org/bpf/bpf-next/c/4145203841ba
- [bpf-next,v6,2/2] selftests/bpf: Add trampolines single and multi-level pointer params test coverage
https://git.kernel.org/bpf/bpf-next/c/e8571de53445
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-03-24 20:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-14 8:21 [PATCH bpf-next v6 0/2] bpf: Add multi-level pointer parameter support for trampolines Slava Imameev
2026-03-14 8:21 ` [PATCH bpf-next v6 1/2] bpf: Support pointer param types via SCALAR_VALUE " Slava Imameev
2026-03-24 20:21 ` Eduard Zingerman
2026-03-14 8:21 ` [PATCH bpf-next v6 2/2] selftests/bpf: Add trampolines single and multi-level pointer params test coverage Slava Imameev
2026-03-24 20:23 ` Eduard Zingerman
2026-03-24 20:40 ` 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=177438481628.1297770.15710276152087682651.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=davem@davemloft.net \
--cc=eddyz87@gmail.com \
--cc=edumazet@google.com \
--cc=haoluo@google.com \
--cc=horms@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-open-source@crowdstrike.com \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=slava.imameev@crowdstrike.com \
--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