From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Paul Chaignon <paul.chaignon@gmail.com>
Cc: stable@vger.kernel.org, Eduard Zingerman <eddyz87@gmail.com>,
Alexei Starovoitov <ast@kernel.org>,
Shung-Hsi Yu <shung-hsi.yu@suse.com>
Subject: Re: [PATCH stable 6.6 0/6] bpf: Fix bounds when ranges cross sign boundary
Date: Sat, 4 Apr 2026 08:23:34 +0200 [thread overview]
Message-ID: <2026040428-request-coastline-6a99@gregkh> (raw)
In-Reply-To: <adArq7uWVYwwTR_4@mail.gmail.com>
On Fri, Apr 03, 2026 at 11:05:47PM +0200, Paul Chaignon wrote:
> On Fri, Apr 03, 2026 at 05:33:59PM +0200, Paul Chaignon wrote:
> > As discussed in [1] yesterday, this series backports two sets of fixes
> > for BPF, with their selftests:
> > - 00bf8d0c6c9b ("bpf: Improve bounds when s64 crosses sign boundary")
> > - 26e5e346a52c ("selftests/bpf: Test cross-sign 64bits range
> > refinement")
> > - f96841bbf4a1 ("selftests/bpf: Test invariants on JSLT crossing sign")
> > - 5dbb19b16ac4 ("bpf: Add third round of bounds deduction")
> > - fbc7aef517d8 ("bpf: Fix u32/s32 bounds when ranges cross min/max
> > boundary")
> > - f81fdfd16771 ("selftests/bpf: test refining u32/s32 bounds when
> > ranges cross min/max boundary")
> >
> > Using Shung-Hsi's stable CI repo [2], I verified the BPF selftests pass
> > with these commits applied on top of v6.12.
>
> As hinted here, the subject prefix is incorrect. This series is meant
> for v6.12, not v6.6. Should I resend?
Yes please!
next prev parent reply other threads:[~2026-04-04 6:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-03 15:33 [PATCH stable 6.6 0/6] bpf: Fix bounds when ranges cross sign boundary Paul Chaignon
2026-04-03 15:35 ` [PATCH stable 6.6 1/6] bpf: Improve bounds when s64 crosses " Paul Chaignon
2026-04-03 15:36 ` [PATCH stable 6.6 2/6] selftests/bpf: Test cross-sign 64bits range refinement Paul Chaignon
2026-04-03 15:37 ` [PATCH stable 6.6 3/6] selftests/bpf: Test invariants on JSLT crossing sign Paul Chaignon
2026-04-03 15:37 ` [PATCH stable 6.6 4/6] bpf: Add third round of bounds deduction Paul Chaignon
2026-04-03 15:37 ` [PATCH stable 6.6 5/6] bpf: Fix u32/s32 bounds when ranges cross min/max boundary Paul Chaignon
2026-04-03 15:37 ` [PATCH stable 6.6 6/6] selftests/bpf: test refining " Paul Chaignon
2026-04-03 21:05 ` [PATCH stable 6.6 0/6] bpf: Fix bounds when ranges cross sign boundary Paul Chaignon
2026-04-04 6:23 ` Greg Kroah-Hartman [this message]
2026-04-04 7:58 ` [PATCH stable 6.12 " Paul Chaignon
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=2026040428-request-coastline-6a99@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=ast@kernel.org \
--cc=eddyz87@gmail.com \
--cc=paul.chaignon@gmail.com \
--cc=shung-hsi.yu@suse.com \
--cc=stable@vger.kernel.org \
/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