From: Eduard Zingerman <eddyz87@gmail.com>
To: Dimitar Kanaliev <dimitar.kanaliev@siteground.com>, bpf@vger.kernel.org
Cc: 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>,
Mykola Lysenko <mykolal@fb.com>,
Yonghong Song <yonghong.song@linux.dev>,
Shung-Hsi Yu <shung-hsi.yu@suse.com>
Subject: Re: [PATCH v0 2/3] bpf: verifier: Simplify register sign extension with tnum_scast
Date: Thu, 30 Jan 2025 15:24:58 -0800 [thread overview]
Message-ID: <99c5181efc1fccb90bb04190abe174abfce8354a.camel@gmail.com> (raw)
In-Reply-To: <20250130112342.69843-3-dimitar.kanaliev@siteground.com>
On Thu, 2025-01-30 at 13:23 +0200, Dimitar Kanaliev wrote:
[...]
> static void coerce_reg_to_size_sx(struct bpf_reg_state *reg, int size)
> {
> - s64 init_s64_max, init_s64_min, s64_max, s64_min, u64_cval;
> - u64 top_smax_value, top_smin_value;
> - u64 num_bits = size * 8;
> + u64 s = size * 8 - 1;
> + u64 sign_mask = 1ULL << s;
> + s64 smin_value, smax_value;
> + u64 umax_value;
>
> - if (tnum_is_const(reg->var_off)) {
> - u64_cval = reg->var_off.value;
> - if (size == 1)
> - reg->var_off = tnum_const((s8)u64_cval);
> - else if (size == 2)
> - reg->var_off = tnum_const((s16)u64_cval);
> - else
> - /* size == 4 */
> - reg->var_off = tnum_const((s32)u64_cval);
> -
> - u64_cval = reg->var_off.value;
> - reg->smax_value = reg->smin_value = u64_cval;
> - reg->umax_value = reg->umin_value = u64_cval;
> - reg->s32_max_value = reg->s32_min_value = u64_cval;
> - reg->u32_max_value = reg->u32_min_value = u64_cval;
> + if (size >= 8)
> return;
> - }
>
> - top_smax_value = ((u64)reg->smax_value >> num_bits) << num_bits;
> - top_smin_value = ((u64)reg->smin_value >> num_bits) << num_bits;
> + reg->var_off = tnum_scast(reg->var_off, size);
>
> - if (top_smax_value != top_smin_value)
> - goto out;
> -
> - /* find the s64_min and s64_min after sign extension */
> - if (size == 1) {
> - init_s64_max = (s8)reg->smax_value;
> - init_s64_min = (s8)reg->smin_value;
> - } else if (size == 2) {
> - init_s64_max = (s16)reg->smax_value;
> - init_s64_min = (s16)reg->smin_value;
> + if (reg->var_off.mask & sign_mask) {
> + smin_value = -(1LL << s);
> + smax_value = (1LL << s) - 1;
> } else {
> - init_s64_max = (s32)reg->smax_value;
> - init_s64_min = (s32)reg->smin_value;
> + smin_value = (s64)(reg->var_off.value);
> + smax_value = (s64)(reg->var_off.value | reg->var_off.mask);
Note the following code in __update_reg64_bounds():
static void __update_reg64_bounds(struct bpf_reg_state *reg)
{
/* min signed is max(sign bit) | min(other bits) */
reg->smin_value = max_t(s64, reg->smin_value,
reg->var_off.value | (reg->var_off.mask & S64_MIN));
/* max signed is min(sign bit) | max(other bits) */
reg->smax_value = min_t(s64, reg->smax_value,
reg->var_off.value | (reg->var_off.mask & S64_MAX));
reg->umin_value = max(reg->umin_value, reg->var_off.value);
reg->umax_value = min(reg->umax_value,
reg->var_off.value | reg->var_off.mask);
}
Is it possible to set {u,s}min/{u,s}max to {U,S}64_MIN/{U,S}64_MAX and rely on
__update_reg64_bounds() for this computation?
> }
>
> - s64_max = max(init_s64_max, init_s64_min);
> - s64_min = min(init_s64_max, init_s64_min);
> + reg->smin_value = smin_value;
> + reg->smax_value = smax_value;
>
> - /* both of s64_max/s64_min positive or negative */
> - if ((s64_max >= 0) == (s64_min >= 0)) {
> - reg->s32_min_value = reg->smin_value = s64_min;
> - reg->s32_max_value = reg->smax_value = s64_max;
> - reg->u32_min_value = reg->umin_value = s64_min;
> - reg->u32_max_value = reg->umax_value = s64_max;
> - reg->var_off = tnum_range(s64_min, s64_max);
> - return;
> - }
> + reg->umin_value = reg->var_off.value;
> + umax_value = reg->var_off.value | reg->var_off.mask;
> + reg->umax_value = umax_value;
>
> -out:
> - set_sext64_default_val(reg, size);
After this commit the functions set_sext64_default_val() and
set_sext32_default_val() are never called.
> + reg->s32_min_value = (s32)smin_value;
> + reg->s32_max_value = (s32)smax_value;
> + reg->u32_min_value = (u32)reg->umin_value;
> + reg->u32_max_value = (u32)umax_value;
> }
[...]
next prev parent reply other threads:[~2025-01-30 23:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-30 11:23 [PATCH v0 0/3] Add tnum_scast helper Dimitar Kanaliev
2025-01-30 11:23 ` [PATCH v0 1/3] bpf: Introduce tnum_scast as a tnum native sign extension helper Dimitar Kanaliev
2025-01-30 21:59 ` Eduard Zingerman
2025-01-30 11:23 ` [PATCH v0 2/3] bpf: verifier: Simplify register sign extension with tnum_scast Dimitar Kanaliev
2025-01-30 23:24 ` Eduard Zingerman [this message]
2025-01-30 11:23 ` [PATCH v0 3/3] selftests/bpf: Extend tests with more coverage for sign extension Dimitar Kanaliev
2025-01-30 22:48 ` Eduard Zingerman
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=99c5181efc1fccb90bb04190abe174abfce8354a.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dimitar.kanaliev@siteground.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=sdf@fomichev.me \
--cc=shung-hsi.yu@suse.com \
--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