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, memxor@gmail.com, npc@anthropic.com
Subject: Re: [PATCH bpf 1/3] bpf: zero extend the result of an arena 32-bit cmpxchg
Date: Fri, 04 Sep 2026 02:00:12 +0000 [thread overview]
Message-ID: <178848721214.4116251.11029484236998441366.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260903171542.1438050-1-eddyz87@gmail.com>
Hello:
This series was applied to bpf/bpf.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 3 Sep 2026 10:15:39 -0700 you wrote:
> bpf_convert_ctx_accesses() rewrites an atomic on an arena pointer from
> BPF_STX | BPF_ATOMIC to BPF_STX | BPF_PROBE_ATOMIC, and it runs before
> bpf_opt_subreg_zext_lo32_rnd_hi32().
>
> That pass emits an explicit zero extension for a 32-bit cmpxchg even
> when bpf_jit_needs_zext() is false. This is done because on some
> architectures 32-bit cmpxchg requires explicit zero extension for the
> dst register. E.g. on x86-64 'lock cmpxchg' does not change the %eax
> if comparison is successful, while BPF semantics declare that each
> operation on a 32-bit register zero extends it's upper half.
>
> [...]
Here is the summary with links:
- [bpf,1/3] bpf: zero extend the result of an arena 32-bit cmpxchg
https://git.kernel.org/bpf/bpf/c/4814ed6406f3
- [bpf,2/3] bpf: update disasm.c to print BPF_PROBE_ATOMIC as atomics
https://git.kernel.org/bpf/bpf/c/1f3cd9719c40
- [bpf,3/3] selftests/bpf: check zero extension of an arena 32-bit cmpxchg
https://git.kernel.org/bpf/bpf/c/54ed91950363
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-09-04 2:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 17:15 [PATCH bpf 1/3] bpf: zero extend the result of an arena 32-bit cmpxchg Eduard Zingerman
2026-09-03 17:15 ` [PATCH bpf 2/3] bpf: update disasm.c to print BPF_PROBE_ATOMIC as atomics Eduard Zingerman
2026-09-03 18:11 ` bot+bpf-ci
2026-09-03 19:38 ` Eduard Zingerman
2026-09-03 17:15 ` [PATCH bpf 3/3] selftests/bpf: check zero extension of an arena 32-bit cmpxchg Eduard Zingerman
2026-09-04 2: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=178848721214.4116251.11029484236998441366.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=kernel-team@fb.com \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=npc@anthropic.com \
--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