From: KaFai Wan <kafai.wan@linux.dev>
To: Eduard Zingerman <eddyz87@gmail.com>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Yonghong Song <yonghong.song@linux.dev>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
John Fastabend <john.fastabend@gmail.com>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Song Liu <song@kernel.org>, KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>, Shuah Khan <shuah@kernel.org>,
Paul Chaignon <paul.chaignon@gmail.com>,
Matan Shachnai <m.shachnai@gmail.com>,
Luis Gerhorst <luis.gerhorst@fau.de>,
colin.i.king@gmail.com,
Harishankar Vishwanathan <harishankar.vishwanathan@gmail.com>,
bpf <bpf@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
Kaiyan Mei <M202472210@hust.edu.cn>,
Yinhao Hu <dddddd@hust.edu.cn>
Subject: Re: [PATCH bpf-next 1/2] bpf: Skip bounds adjustment for conditional jumps on same register
Date: Sat, 25 Oct 2025 00:13:19 +0800 [thread overview]
Message-ID: <b190c9b2837b28cf579aa38126de50e29e0add32.camel@linux.dev> (raw)
In-Reply-To: <f0a52150bc99aa4da1a25d6181975cd3c80a717f.camel@gmail.com>
On Thu, 2025-10-23 at 10:38 -0700, Eduard Zingerman wrote:
> On Thu, 2025-10-23 at 19:26 +0800, KaFai Wan wrote:
>
> [...]
>
> > > @@ -16173,6 +16173,25 @@ static int is_pkt_ptr_branch_taken(struct
> > > bpf_reg_state *dst_reg,
> > > static int is_branch_taken(struct bpf_reg_state *reg1, struct bpf_reg_state
> > > *reg2,
> > > u8 opcode, bool is_jmp32)
> > > {
> > > + if (reg1 == reg2) {
> > > + switch (opcode) {
> > > + case BPF_JGE:
> > > + case BPF_JLE:
> > > + case BPF_JSGE:
> > > + case BPF_JSLE:
> > > + case BPF_JEQ:
> > > + case BPF_JSET:
> >
> > Others are fine, but BPF_JSET on the same register could be 0 (if value is 0).
> > And it's unknown to take the branch if 0 within the range.
>
> Right, missed that one.
>
> >
> > > + return 1;
> > > + case BPF_JGT:
> > > + case BPF_JLT:
> > > + case BPF_JSGT:
> > > + case BPF_JSLT:
> > > + case BPF_JNE:
> > > + return 0;
> > > + default:
> > > + return -1;
> > > + }
> > > + }
> > >
> > > But that's too much code for an artificial case.
> > > Idk, either way is fine with me.
> >
> > There is is_scalar_branch_taken() in is_branch_taken(), I missed it. I'll a)
> > check the opcode one by one in is_scalar_branch_taken(), and b) keep this patch
> > for unknown BPF_JSET branch.
>
> Sounds good to me. Note that the logic is correct for both scalar and
> non-scalar cases, so I don't think we have to constrain it to
> is_scalar_branch_taken() (don't think there is a need to check if
> pointer comparisons are allowed, as no new information is inferred
> from comparisons with self).
For non-scalar cases we only allow pointer comparison on pkt_ptr, this check is before
is_branch_taken()
src_reg = ®s[insn->src_reg];
if (!(reg_is_pkt_pointer_any(dst_reg) && reg_is_pkt_pointer_any(src_reg)) &&
is_pointer_value(env, insn->src_reg)) {
verbose(env, "R%d pointer comparison prohibited\n",
insn->src_reg);
return -EACCES;
}
and in the end of check_cond_jmp_op() (after is_branch_taken()), we checked again
} else if (!try_match_pkt_pointers(insn, dst_reg, ®s[insn->src_reg],
this_branch, other_branch) &&
is_pointer_value(env, insn->dst_reg)) {
verbose(env, "R%d pointer comparison prohibited\n",
insn->dst_reg);
return -EACCES;
}
this time we check if it is valid comparison on pkt_ptr in try_match_pkt_pointers().
Currently we just allow 4 opcode (BPF_JGT, BPF_JLT, BPF_JGE, BPF_JLE) on pkt_ptr, and with
conditions. But we bypass these prohibits in privileged mode (is_pointer_value() always
return false in privileged mode).
So the logic skip these prohibits for pkt_ptr in unprivileged mode.
--
Thanks,
KaFai
next prev parent reply other threads:[~2025-10-24 16:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-22 16:44 [PATCH bpf-next 0/2] bpf: Skip bounds adjustment for conditional jumps on same register KaFai Wan
2025-10-22 16:44 ` [PATCH bpf-next 1/2] " KaFai Wan
2025-10-22 18:14 ` Yonghong Song
2025-10-22 19:46 ` Eduard Zingerman
2025-10-22 20:12 ` Alexei Starovoitov
2025-10-22 20:30 ` Eduard Zingerman
2025-10-22 20:34 ` Alexei Starovoitov
2025-10-23 11:26 ` KaFai Wan
2025-10-23 17:38 ` Eduard Zingerman
2025-10-24 16:13 ` KaFai Wan [this message]
2025-10-24 16:21 ` Eduard Zingerman
2025-10-24 16:37 ` KaFai Wan
2025-10-24 16:40 ` Alexei Starovoitov
2025-10-24 16:53 ` KaFai Wan
2025-10-22 16:44 ` [PATCH bpf-next 2/2] selftests/bpf: Add test " KaFai Wan
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=b190c9b2837b28cf579aa38126de50e29e0add32.camel@linux.dev \
--to=kafai.wan@linux.dev \
--cc=M202472210@hust.edu.cn \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=colin.i.king@gmail.com \
--cc=daniel@iogearbox.net \
--cc=dddddd@hust.edu.cn \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=harishankar.vishwanathan@gmail.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=luis.gerhorst@fau.de \
--cc=m.shachnai@gmail.com \
--cc=martin.lau@linux.dev \
--cc=paul.chaignon@gmail.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--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