From: Puranjay Mohan <puranjay@kernel.org>
To: Daniel Borkmann <daniel@iogearbox.net>, memxor@gmail.com
Cc: eddyz87@gmail.com, bpf@vger.kernel.org,
Puranjay Mohan <puranjay12@gmail.com>
Subject: Re: [PATCH bpf-next 3/6] bpf, x86: Clear fetch destination on faulting arena atomic
Date: Mon, 10 Aug 2026 19:22:35 +0100 [thread overview]
Message-ID: <m2zeytj0no.fsf@kernel.org> (raw)
In-Reply-To: <20260810134346.466004-3-daniel@iogearbox.net>
Daniel Borkmann <daniel@iogearbox.net> writes:
> populate_extable() encodes "there is no destination register to clear" as
> DONT_CLEAR in the DST_REG field of the exception table metadata, and later
> ex_handler_bpf() then reuses that very value to derive the direction it
> reports the fault with is_write = (reg == DONT_CLEAR). The two coincide
> for a plain load or store, but not for a RMW carrying BPF_FETCH. Such an
> atomic writes memory, so it has to be reported as a WRITE, and it also reads
> the old value into a register, src_reg for BPF_ADD | BPF_FETCH and BPF_XCHG,
> r0 for BPF_CMPXCHG, so that register has to be cleared on fault. A single
> DONT_CLEAR cannot say both, and the store branch picks it unconditionally:
>
> [...]
> } else {
> arena_reg = reg2pt_regs[dst_reg];
> fixup_reg = DONT_CLEAR;
> }
> [...]
>
> The reported direction is therefore right, but on a fault over an unmapped
> arena page the fetch destination keeps whatever it held before the atomic,
> where every other BPF_PROBE_* access delivers 0. Give the metadata its own
> ARENA_WRITE bit so that the reported direction no longer depends on whether
> there is a register to clear, and fill DST_REG in from bpf_atomic_load_reg().
> BPF_{AND,OR,XOR} | BPF_FETCH need no handling here, bpf_jit_supports_insn()
> already rejects those in the arena.
>
> Fixes: d503a04f8bc0 ("bpf: Add support for certain atomics in bpf_arena to x86 JIT")
> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
> ---
> arch/x86/net/bpf_jit_comp.c | 35 +++++++++++++++++++++++++++--------
> 1 file changed, 27 insertions(+), 8 deletions(-)
>
> diff --git a/arch/x86/net/bpf_jit_comp.c b/arch/x86/net/bpf_jit_comp.c
> index 8dddb5d7af21..d920772af7d5 100644
> --- a/arch/x86/net/bpf_jit_comp.c
> +++ b/arch/x86/net/bpf_jit_comp.c
> @@ -1473,17 +1473,20 @@ static int emit_atomic_ld_st_index(u8 **pprog, u32 atomic_op, u32 size,
> *
> * Bit layout of `fixup` (32-bit):
> *
> - * +-----------+--------+-----------+---------+----------+
> - * | 31 | 30-24 | 23-16 | 15-8 | 7-0 |
> - * | | | | | |
> - * | ARENA_ACC | Unused | ARENA_REG | DST_REG | INSN_LEN |
> - * +-----------+--------+-----------+---------+----------+
> + * +-----------+-------------+--------+-----------+---------+----------+
> + * | 31 | 30 | 29-24 | 23-16 | 15-8 | 7-0 |
> + * | | | | | | |
> + * | ARENA_ACC | ARENA_WRITE | Unused | ARENA_REG | DST_REG | INSN_LEN |
> + * +-----------+-------------+--------+-----------+---------+----------+
> *
> * - INSN_LEN (8 bits): Length of faulting insn (max x86 insn = 15 bytes (fits in 8 bits)).
> * - DST_REG (8 bits): Offset of dst_reg from reg2pt_regs[] (max offset = 112 (fits in 8 bits)).
> - * This is set to DONT_CLEAR if the insn is a store.
> + * This is set to DONT_CLEAR if the insn does not read into a register.
> * - ARENA_REG (8 bits): Offset of the register that is used to calculate the
> * address for load/store when accessing the arena region.
> + * - ARENA_WRITE (1 bit): This bit is set when the faulting instruction wrote to the arena region.
> + * It is independent of DST_REG, since a read-modify-write both writes to
> + * memory and reads the old value into a register.
> * - ARENA_ACCESS (1 bit): This bit is set when the faulting instruction accessed the arena region.
> *
> * Bit layout of `data` (32-bit):
> @@ -1502,6 +1505,7 @@ static int emit_atomic_ld_st_index(u8 **pprog, u32 atomic_op, u32 size,
> #define FIXUP_INSN_LEN_MASK GENMASK(7, 0)
> #define FIXUP_REG_MASK GENMASK(15, 8)
> #define FIXUP_ARENA_REG_MASK GENMASK(23, 16)
> +#define FIXUP_ARENA_WRITE BIT(30)
> #define FIXUP_ARENA_ACCESS BIT(31)
> #define DATA_ARENA_OFFSET_MASK GENMASK(31, 16)
>
> @@ -1510,7 +1514,7 @@ bool ex_handler_bpf(const struct exception_table_entry *x, struct pt_regs *regs)
> u32 reg = FIELD_GET(FIXUP_REG_MASK, x->fixup);
> u32 insn_len = FIELD_GET(FIXUP_INSN_LEN_MASK, x->fixup);
> bool is_arena = !!(x->fixup & FIXUP_ARENA_ACCESS);
> - bool is_write = (reg == DONT_CLEAR);
> + bool is_write = !!(x->fixup & FIXUP_ARENA_WRITE);
> unsigned long addr;
> s16 off;
> u32 arena_reg;
> @@ -2348,6 +2352,7 @@ st: insn_off = insn->off;
> struct exception_table_entry *ex;
> u8 *_insn = image + proglen + (start_of_ldx - temp);
> u32 arena_reg, fixup_reg;
> + bool is_write;
> s64 delta;
>
> if (!bpf_prog->aux->extable)
> @@ -2384,15 +2389,29 @@ st: insn_off = insn->off;
> bpf_atomic_is_load_acq(insn)) {
> arena_reg = reg2pt_regs[src_reg];
> fixup_reg = reg2pt_regs[dst_reg];
> + is_write = false;
> } else {
> + /*
> + * A store has no destination register to clear,
> + * except for a read-modify-write with BPF_FETCH,
> + * which also reads the old value into src_reg, or
> + * into r0 for a BPF_CMPXCHG. Either way the access
> + * is still reported as a write.
> + */
> + int load_reg = bpf_atomic_load_reg(insn);
> +
> arena_reg = reg2pt_regs[dst_reg];
> - fixup_reg = DONT_CLEAR;
> + fixup_reg = load_reg < 0 ? DONT_CLEAR :
> + reg2pt_regs[load_reg];
> + is_write = true;
> }
>
> ex->fixup = FIELD_PREP(FIXUP_INSN_LEN_MASK, prog - start_of_ldx) |
> FIELD_PREP(FIXUP_ARENA_REG_MASK, arena_reg) |
> FIELD_PREP(FIXUP_REG_MASK, fixup_reg);
> ex->fixup |= FIXUP_ARENA_ACCESS;
> + if (is_write)
> + ex->fixup |= FIXUP_ARENA_WRITE;
>
> ex->data |= FIELD_PREP(DATA_ARENA_OFFSET_MASK, insn->off);
> }
> --
> 2.43.0
Reviewed-by: Puranjay Mohan <puranjay@kernel.org>
next prev parent reply other threads:[~2026-08-10 18:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-10 13:43 [PATCH bpf-next 1/6] bpf: Derive the atomic load register in one place Daniel Borkmann
2026-08-10 13:43 ` [PATCH bpf-next 2/6] bpf, riscv: Clear fetch destination on faulting arena atomic Daniel Borkmann
2026-08-10 13:43 ` [PATCH bpf-next 3/6] bpf, x86: " Daniel Borkmann
2026-08-10 14:07 ` sashiko-bot
2026-08-10 14:08 ` Daniel Borkmann
2026-08-10 17:26 ` Eduard Zingerman
2026-08-10 18:22 ` Puranjay Mohan [this message]
2026-08-10 13:43 ` [PATCH bpf-next 4/6] bpf, arm64: " Daniel Borkmann
2026-08-10 18:20 ` Eduard Zingerman
2026-08-10 18:30 ` Puranjay Mohan
2026-08-10 18:36 ` Eduard Zingerman
2026-08-10 18:31 ` Puranjay Mohan
2026-08-10 13:43 ` [PATCH bpf-next 5/6] bpf, s390: " Daniel Borkmann
2026-08-10 13:43 ` [PATCH bpf-next 6/6] selftests/bpf: Add arena fault tests for atomics with fetch Daniel Borkmann
2026-08-10 18:56 ` Eduard Zingerman
2026-08-10 15:08 ` [PATCH bpf-next 1/6] bpf: Derive the atomic load register in one place bot+bpf-ci
2026-08-10 17:10 ` Eduard Zingerman
2026-08-10 18:13 ` Daniel Borkmann
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=m2zeytj0no.fsf@kernel.org \
--to=puranjay@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=memxor@gmail.com \
--cc=puranjay12@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