From: patchwork-bot+netdevbpf@kernel.org
To: Jiri Olsa <jolsa@kernel.org>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
oliver.sang@intel.com, paul.chaignon@gmail.com,
bpf@vger.kernel.org, linux-perf-users@vger.kernel.org,
kafai@fb.com, eddyz87@gmail.com, songliubraving@fb.com,
yhs@fb.com, john.fastabend@gmail.com, haoluo@google.com
Subject: Re: [PATCHv3 bpf] bpf: Check the helper function is valid in get_helper_proto
Date: Fri, 15 Aug 2025 09:20:07 +0000 [thread overview]
Message-ID: <175524960701.1002181.5903388173238461777.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250814200655.945632-1-jolsa@kernel.org>
Hello:
This patch was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Thu, 14 Aug 2025 22:06:55 +0200 you wrote:
> From: Jiri Olsa <olsajiri@gmail.com>
>
> kernel test robot reported verifier bug [1] where the helper func
> pointer could be NULL due to disabled config option.
>
> As Alexei suggested we could check on that in get_helper_proto
> directly. Marking tail_call helper func with BPF_PTR_POISON,
> because it is unused by design.
>
> [...]
Here is the summary with links:
- [PATCHv3,bpf] bpf: Check the helper function is valid in get_helper_proto
https://git.kernel.org/bpf/bpf/c/e4414b01c1cd
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:[~2025-08-15 9:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 20:06 [PATCHv3 bpf] bpf: Check the helper function is valid in get_helper_proto Jiri Olsa
2025-08-15 9:20 ` 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=175524960701.1002181.5903388173238461777.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=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=oliver.sang@intel.com \
--cc=paul.chaignon@gmail.com \
--cc=songliubraving@fb.com \
--cc=yhs@fb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.