From: Peilin Ye <yepeilin@google.com>
To: Eduard Zingerman <eddyz87@gmail.com>
Cc: bpf@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
bpf@ietf.org, Xu Kuohai <xukuohai@huaweicloud.com>,
David Vernet <void@manifault.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>,
Yonghong Song <yonghong.song@linux.dev>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
"Paul E. McKenney" <paulmck@kernel.org>,
Puranjay Mohan <puranjay@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Quentin Monnet <qmo@kernel.org>,
Mykola Lysenko <mykolal@fb.com>, Shuah Khan <shuah@kernel.org>,
Josh Don <joshdon@google.com>, Barret Rhoden <brho@google.com>,
Neel Natu <neelnatu@google.com>,
Benjamin Segall <bsegall@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v1 3/8] bpf: Introduce load-acquire and store-release instructions
Date: Wed, 29 Jan 2025 22:04:53 +0000 [thread overview]
Message-ID: <Z5qmBaGE4a7NtaFU@google.com> (raw)
In-Reply-To: <b7de0135f7dcca0485ce9dc853d6ca812c30244b.camel@gmail.com>
On Tue, Jan 28, 2025 at 04:19:25PM -0800, Eduard Zingerman wrote:
> On Sat, 2025-01-25 at 02:18 +0000, Peilin Ye wrote:
> > Signed-off-by: Peilin Ye <yepeilin@google.com>
> > ---
>
> I think bpf_jit_supports_insn() in arch/{x86,s390}/net/bpf_jit_comp.c
> need an update, as both would accept BPF_LOAD_ACQ/BPF_STORE_REL at the
> moment.
Got it - I will move is_atomic_load_store() into <linux/bpf.h> for that.
> Acked-by: Eduard Zingerman <eddyz87@gmail.com>
Thanks!
> > +static int check_atomic_load(struct bpf_verifier_env *env, int insn_idx,
> > + struct bpf_insn *insn)
> > +{
> > + struct bpf_reg_state *regs = cur_regs(env);
> > + int err;
> > +
> > + err = check_reg_arg(env, insn->src_reg, SRC_OP);
> > + if (err)
> > + return err;
> > +
> > + err = check_reg_arg(env, insn->dst_reg, DST_OP_NO_MARK);
> > + if (err)
> > + return err;
> > +
> > + if (!atomic_ptr_type_ok(env, insn->src_reg, insn)) {
> > + verbose(env, "BPF_ATOMIC loads from R%d %s is not allowed\n",
> > + insn->src_reg,
> > + reg_type_str(env, reg_state(env, insn->src_reg)->type));
> > + return -EACCES;
> > + }
> > +
> > + if (is_arena_reg(env, insn->src_reg)) {
> > + err = save_aux_ptr_type(env, PTR_TO_ARENA, false);
> > + if (err)
> > + return err;
>
> Nit: this and the next function look very similar to processing of
> generic load and store in do_check(). Maybe extract that code
> as an auxiliary function and call it in both places?
Sure, I agree that they look a bit repetitive.
> The only major difference is is_arena_reg() check guarding
> save_aux_ptr_type(), but I think it is ok to do save_aux_ptr_type
> unconditionally. Fwiw, the code would be a bit simpler,
> just spent half an hour convincing myself that such conditional handling
> is not an error. Wdyt?
:-O
Thanks a lot for that; would you mind sharing a bit more on how you
reasoned about it (i.e., why is it OK to save_aux_ptr_type()
unconditionally) ?
> > + }
> > +
> > + /* Check whether we can read the memory. */
> > + err = check_mem_access(env, insn_idx, insn->src_reg, insn->off,
> > + BPF_SIZE(insn->code), BPF_READ, insn->dst_reg,
> > + true, false);
> > + if (err)
> > + return err;
> > +
> > + err = reg_bounds_sanity_check(env, ®s[insn->dst_reg], "atomic_load");
> > + if (err)
> > + return err;
> > + return 0;
> > +}
> > +
> > +static int check_atomic_store(struct bpf_verifier_env *env, int insn_idx,
> > + struct bpf_insn *insn)
Thanks,
Peilin Ye
next prev parent reply other threads:[~2025-01-29 22:04 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-25 2:16 [PATCH bpf-next v1 0/8] Introduce load-acquire and store-release BPF instructions Peilin Ye
2025-01-25 2:17 ` [PATCH bpf-next v1 1/8] bpf/verifier: Factor out atomic_ptr_type_ok() Peilin Ye
2025-01-25 2:18 ` [PATCH bpf-next v1 2/8] bpf/verifier: Factor out check_atomic_rmw() Peilin Ye
2025-01-25 2:18 ` [PATCH bpf-next v1 3/8] bpf: Introduce load-acquire and store-release instructions Peilin Ye
2025-01-29 0:19 ` Eduard Zingerman
2025-01-29 22:04 ` Peilin Ye [this message]
2025-01-29 22:42 ` Eduard Zingerman
2025-01-30 3:10 ` Peilin Ye
2025-01-29 1:30 ` Eduard Zingerman
2025-01-29 22:17 ` Peilin Ye
2025-01-30 0:41 ` Alexei Starovoitov
2025-01-30 3:38 ` Peilin Ye
2025-01-25 2:18 ` [PATCH bpf-next v1 4/8] arm64: insn: Add BIT(23) to {load,store}_ex's mask Peilin Ye
2025-01-25 2:19 ` [PATCH bpf-next v1 5/8] arm64: insn: Add load-acquire and store-release instructions Peilin Ye
2025-01-25 2:19 ` [PATCH bpf-next v1 6/8] bpf, arm64: Support " Peilin Ye
2025-01-25 2:19 ` [PATCH bpf-next v1 7/8] selftests/bpf: Add selftests for " Peilin Ye
2025-01-29 1:06 ` Eduard Zingerman
2025-01-29 2:07 ` Ihor Solodrai
2025-01-29 2:07 ` [Bpf] " Ihor Solodrai
2025-01-29 2:17 ` Eduard Zingerman
2025-01-30 0:03 ` Peilin Ye
2025-02-04 0:30 ` Peilin Ye
2025-02-04 0:52 ` Eduard Zingerman
2025-02-04 1:29 ` Peilin Ye
2025-01-25 2:19 ` [PATCH bpf-next v1 8/8] bpf, docs: Update instruction-set.rst " Peilin Ye
2025-01-30 0:44 ` Alexei Starovoitov
2025-01-30 7:33 ` Peilin Ye
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=Z5qmBaGE4a7NtaFU@google.com \
--to=yepeilin@google.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@ietf.org \
--cc=bpf@vger.kernel.org \
--cc=brho@google.com \
--cc=bsegall@google.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=joshdon@google.com \
--cc=kpsingh@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=neelnatu@google.com \
--cc=paulmck@kernel.org \
--cc=puranjay@kernel.org \
--cc=qmo@kernel.org \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=void@manifault.com \
--cc=will@kernel.org \
--cc=xukuohai@huaweicloud.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;
as well as URLs for NNTP newsgroup(s).