From: Eduard Zingerman <eddyz87@gmail.com>
To: Helen Koike <koike@igalia.com>, Shung-Hsi Yu <shung-hsi.yu@suse.com>
Cc: andrii@kernel.org, yonghong.song@linux.dev, ast@kernel.org,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-dev@igalia.com
Subject: Re: [PATCH 1/2] bpf: deduce_bounds_64_from_32 tightening with circular range logic
Date: Tue, 14 Apr 2026 11:32:20 -0700 [thread overview]
Message-ID: <2aaf049fdd735f642f470ca6b0822bddf07a5eff.camel@gmail.com> (raw)
In-Reply-To: <aa97dc1f-02d2-4da6-aa17-9619e2b6f999@igalia.com>
On Tue, 2026-04-14 at 13:25 -0300, Helen Koike wrote:
> Hi Shung-Hsi Yu,
>
>
> Thanks for your reply,
>
> On 4/14/26 5:26 AM, Shung-Hsi Yu wrote:
> > Hi Helen,
> >
> > On Fri, Apr 10, 2026 at 09:40:27AM -0300, Helen Koike wrote:
> > ...
> > > This is a follow-up from discussion:
> > > https://lore.kernel.org/all/7fb97184-baaa-4639-a0b9-ac289bf2e54d@igalia.com/
> >
> > Base on the original thread, I see that motivation of the patchset came
> > from a Syzkaller reported issue[1]. Can you try to run the reproducer
> > again and see if you can still get it to reproduce on the bpf-next tree?
>
> I just tested on bpf-next/master ("71b500afd2f7") and I couldn't
> reproduce the issue from Syzbot anymore. It seems that the branch
> causing the issue is pruned now, fixing the error in that case.
>
> But I still get the failures of the kselftests from patch 2/2:
>
> * verifier_bounds/deduce64_from_32_block_change:FAIL
> * verifier_bounds/deduce64_from_32_block_change_signed:FAIL
> *
> verifier_bounds/deduce64_from_32_block_change_conservative_signed:FAIL
> * verifier_bounds/deduce64_from_32_wrapping_32bit:FAIL
>
>
> How do you suggest we should proceed?
>
I still want this for the sake of improved value tracking.
Please give me a bit more time for review.
next prev parent reply other threads:[~2026-04-14 18:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 12:40 [PATCH 1/2] bpf: deduce_bounds_64_from_32 tightening with circular range logic Helen Koike
2026-04-10 12:40 ` [PATCH 2/2] selftests/bpf: new cases handled by 32->64 range refinements Helen Koike
2026-04-14 8:26 ` [PATCH 1/2] bpf: deduce_bounds_64_from_32 tightening with circular range logic Shung-Hsi Yu
2026-04-14 16:25 ` Helen Koike
2026-04-14 18:32 ` Eduard Zingerman [this message]
2026-04-15 7:12 ` Eduard Zingerman
2026-04-15 16:19 ` Harishankar Vishwanathan
2026-04-15 18:12 ` Eduard Zingerman
2026-04-16 3:52 ` Shung-Hsi Yu
2026-04-16 7:43 ` Eduard Zingerman
2026-04-16 13:45 ` Paul Chaignon
2026-04-15 18:12 ` 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=2aaf049fdd735f642f470ca6b0822bddf07a5eff.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=kernel-dev@igalia.com \
--cc=koike@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shung-hsi.yu@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.