From: patchwork-bot+netdevbpf@kernel.org
To: Woojin Ji <random6.xyz@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
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, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf v2 0/2] bpf: Zero-extend the index in inlined bpf_get_func_arg()
Date: Sun, 18 Oct 2026 15:30:06 +0000 [thread overview]
Message-ID: <179233740603.1716327.12837007566420254836.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261018-get-func-arg-v2-0-048848b3eddf@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sun, 18 Oct 2026 13:21:40 +0900 you wrote:
> v2, from the review of v1:
>
> - Shift the index as a 32-bit value instead of inserting an explicit
> zero-extension (Alexei). The inlined sequence is one instruction shorter
> and the bounds check is untouched, so no program is accepted or rejected
> differently.
>
> [...]
Here is the summary with links:
- [bpf,v2,1/2] bpf: Zero-extend the index in inlined bpf_get_func_arg()
https://git.kernel.org/bpf/bpf-next/c/1c1dda9ba9f3
- [bpf,v2,2/2] selftests/bpf: Test out-of-range index bits in bpf_get_func_arg()
https://git.kernel.org/bpf/bpf-next/c/38dbc3047a2f
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-18 15:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 4:21 Woojin Ji
2026-10-18 4:21 ` [PATCH bpf v2 1/2] " Woojin Ji
2026-10-18 4:55 ` bot+bpf-ci
2026-10-18 4:21 ` [PATCH bpf v2 2/2] selftests/bpf: Test out-of-range index bits in bpf_get_func_arg() Woojin Ji
2026-10-18 15: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=179233740603.1716327.12837007566420254836.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=emil@etsalapatis.com \
--cc=ihor.solodrai@linux.dev \
--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=random6.xyz@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®