public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Chaignon <paul.chaignon@gmail.com>
To: Eduard Zingerman <eddyz87@gmail.com>
Cc: Harishankar Vishwanathan <harishankar.vishwanathan@gmail.com>,
	andrii@kernel.org, ast@kernel.org, bpf@vger.kernel.org,
	daniel@iogearbox.net, santosh.nagarakatte@rutgers.edu,
	shung-hsi.yu@suse.com, srinivas.narayana@rutgers.edu
Subject: Re: [PATCH v2 bpf-next 3/6] bpf: Exit early if reg_bounds_sync gets invalid inputs
Date: Wed, 1 Apr 2026 23:19:53 +0200	[thread overview]
Message-ID: <ac2L-Rh_JcZ16qbv@mail.gmail.com> (raw)
In-Reply-To: <4343ab08efc55d52b95f1618dbd367952f8e6a1b.camel@gmail.com>

On Wed, Apr 01, 2026 at 01:21:02PM -0700, Eduard Zingerman wrote:
> On Wed, 2026-04-01 at 15:36 -0400, Harishankar Vishwanathan wrote:
> > On Wed, Apr 1, 2026 at 8:21 AM Paul Chaignon <paul.chaignon@gmail.com> wrote:

[...]

> What are remaining steps for this patch-set?
> Here are outstanding comments:
> 1. https://lore.kernel.org/bpf/33c006d7275cb443b5750f062cb78c38449a7537.camel@gmail.com/
>    resolved as noop
> 2. https://lore.kernel.org/bpf/ed85ac25cd315ac4273de335943f9f3a2c1f36e8.camel@gmail.com/
>    resolved, only if inputs are in bogus state, will be handled by a follow-up.
> 3. https://lore.kernel.org/bpf/7vwyzvy7cwy2n4c52fcurg4dnv4bqijtovmkeh3zgu6ey266vc@dtt3r5usvev5/
>    Some wording nits, do you intend to fix those?
> 4. https://lore.kernel.org/bpf/847173114a13630e1512ad05375c6b407720a916.camel@gmail.com/
>    Will be resolved as a follow-up.
> 5. https://lore.kernel.org/bpf/87ikamjv5q.fsf@gmail.com/
>    resolved as noop.
> 
> Is the above assessment correct?
> Beside (3) is there anything you'd like to change or should we go with v2?

I think there were also a couple nits on the selftests and at
https://lore.kernel.org/bpf/87qzpak4wc.fsf@gmail.com/. Let me send a v3
tomorrow morning with all the small things and the acks :)


  reply	other threads:[~2026-04-01 21:19 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-20 16:45 [PATCH v2 bpf-next 0/6] Fix invariant violations and improve branch detection Paul Chaignon
2026-03-20 16:47 ` [PATCH v2 bpf-next 1/6] bpf: Refactor reg_bounds_sanity_check Paul Chaignon
2026-03-23  8:01   ` Shung-Hsi Yu
2026-03-23 14:16   ` Mykyta Yatsenko
2026-03-24 16:56     ` Harishankar Vishwanathan
2026-03-24 18:16       ` Mykyta Yatsenko
2026-03-20 16:49 ` [PATCH v2 bpf-next 2/6] bpf: Use bpf_verifier_env buffers for reg_set_min_max Paul Chaignon
2026-03-23  8:15   ` Shung-Hsi Yu
2026-03-23 15:33   ` Mykyta Yatsenko
2026-03-23 18:42   ` Eduard Zingerman
2026-03-30 12:05     ` Paul Chaignon
2026-03-31  1:51       ` Eduard Zingerman
2026-03-31 14:56         ` Paul Chaignon
2026-03-31 14:28       ` KaFai Wan
2026-04-01 11:15         ` Paul Chaignon
2026-03-20 16:49 ` [PATCH v2 bpf-next 3/6] bpf: Exit early if reg_bounds_sync gets invalid inputs Paul Chaignon
2026-03-23 12:12   ` Shung-Hsi Yu
2026-03-24 17:46     ` Harishankar Vishwanathan
2026-03-23 18:47   ` Eduard Zingerman
2026-03-24 19:28     ` Harishankar Vishwanathan
2026-03-24 19:33       ` Eduard Zingerman
2026-04-01 12:21         ` Paul Chaignon
2026-04-01 19:36           ` Harishankar Vishwanathan
2026-04-01 20:21             ` Eduard Zingerman
2026-04-01 21:19               ` Paul Chaignon [this message]
2026-03-20 16:49 ` [PATCH v2 bpf-next 4/6] bpf: Simulate branches to prune based on range violations Paul Chaignon
2026-03-23 12:23   ` Shung-Hsi Yu
2026-03-23 16:19   ` Mykyta Yatsenko
2026-03-24 20:36     ` Harishankar Vishwanathan
2026-03-25 13:52       ` Mykyta Yatsenko
2026-03-23 19:05   ` Eduard Zingerman
2026-03-24 23:59     ` Harishankar Vishwanathan
2026-03-25  0:08       ` Eduard Zingerman
2026-03-20 16:50 ` [PATCH v2 bpf-next 5/6] selftests/bpf: Cover invariant violation cases from syzbot Paul Chaignon
2026-03-23 17:46   ` Mykyta Yatsenko
2026-03-28 16:20     ` Paul Chaignon
2026-03-28 17:31       ` Alexei Starovoitov
2026-03-20 16:50 ` [PATCH v2 bpf-next 6/6] selftests/bpf: Remove invariant violation flags Paul Chaignon
2026-03-23 18:04   ` Mykyta Yatsenko

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=ac2L-Rh_JcZ16qbv@mail.gmail.com \
    --to=paul.chaignon@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=harishankar.vishwanathan@gmail.com \
    --cc=santosh.nagarakatte@rutgers.edu \
    --cc=shung-hsi.yu@suse.com \
    --cc=srinivas.narayana@rutgers.edu \
    /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