From: patchwork-bot+netdevbpf@kernel.org
To: Eduard Zingerman <eddyz87@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, martin.lau@linux.dev, kernel-team@fb.com,
yonghong.song@linux.dev, alexei.starovoitov@gmail.com
Subject: Re: [PATCH bpf-next v1 1/2] bpf: avoid jump misprediction for PTR_TO_MEM | PTR_UNTRUSTED
Date: Wed, 02 Jul 2025 15:00:19 +0000 [thread overview]
Message-ID: <175146841979.753088.11975033328524632760.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250702073620.897517-1-eddyz87@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 2 Jul 2025 00:36:19 -0700 you wrote:
> Commit f2362a57aeff ("bpf: allow void* cast using bpf_rdonly_cast()")
> added a notion of PTR_TO_MEM | MEM_RDONLY | PTR_UNTRUSTED type.
> This simultaneously introduced a bug in jump prediction logic for
> situations like below:
>
> p = bpf_rdonly_cast(..., 0);
> if (p) a(); else b();
>
> [...]
Here is the summary with links:
- [bpf-next,v1,1/2] bpf: avoid jump misprediction for PTR_TO_MEM | PTR_UNTRUSTED
https://git.kernel.org/bpf/bpf-next/c/c8313bad6d24
- [bpf-next,v1,2/2] selftests/bpf: null checks for rdonly_untrusted_mem should be preserved
https://git.kernel.org/bpf/bpf-next/c/621af1928153
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-07-02 14:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 7:36 [PATCH bpf-next v1 1/2] bpf: avoid jump misprediction for PTR_TO_MEM | PTR_UNTRUSTED Eduard Zingerman
2025-07-02 7:36 ` [PATCH bpf-next v1 2/2] selftests/bpf: null checks for rdonly_untrusted_mem should be preserved Eduard Zingerman
2025-07-02 15: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=175146841979.753088.11975033328524632760.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=kernel-team@fb.com \
--cc=martin.lau@linux.dev \
--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