From: patchwork-bot+netdevbpf@kernel.org
To: Qi Tang <tpluszz77@gmail.com>
Cc: ast@kernel.org, daniel@iogearbox.net, memxor@gmail.com,
ameryhung@gmail.com, eddyz87@gmail.com, andrii@kernel.org,
martin.lau@linux.dev, song@kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next] selftests/bpf: add test for nullable PTR_TO_BUF access
Date: Tue, 07 Apr 2026 23:00:05 +0000 [thread overview]
Message-ID: <177560280529.4188799.15135394423120356900.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260407145421.4315-1-tpluszz77@gmail.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 7 Apr 2026 22:54:21 +0800 you wrote:
> Add iter_buf_null_fail with two tests and a test runner:
> - iter_buf_null_deref: verifier must reject direct dereference of
> ctx->key (PTR_TO_BUF | PTR_MAYBE_NULL) without a null check
> - iter_buf_null_check_ok: verifier must accept dereference after
> an explicit null check
>
> Acked-by: Kumar Kartikeya Dwivedi <memxor@gmail.com>
> Reviewed-by: Amery Hung <ameryhung@gmail.com>
> Signed-off-by: Qi Tang <tpluszz77@gmail.com>
>
> [...]
Here is the summary with links:
- [bpf-next] selftests/bpf: add test for nullable PTR_TO_BUF access
https://git.kernel.org/bpf/bpf-next/c/a4985a1755ec
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-04-07 23:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 14:54 [PATCH bpf-next] selftests/bpf: add test for nullable PTR_TO_BUF access Qi Tang
2026-04-07 23:00 ` 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=177560280529.4188799.15135394423120356900.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=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=song@kernel.org \
--cc=tpluszz77@gmail.com \
/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