public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Chaignon <paul.chaignon@gmail.com>
To: stable@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Eduard Zingerman <eddyz87@gmail.com>,
	Alexei Starovoitov <ast@kernel.org>,
	Shung-Hsi Yu <shung-hsi.yu@suse.com>
Subject: [PATCH stable 6.6 0/6] bpf: Fix bounds when ranges cross sign boundary
Date: Fri, 3 Apr 2026 17:33:59 +0200	[thread overview]
Message-ID: <cover.1775206731.git.paul.chaignon@gmail.com> (raw)

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.

1: https://lore.kernel.org/stable/2026040240-friday-gurgling-7088@gregkh/
2: https://github.com/pchaigno/stable-bpf-ci/actions/runs/23940850516/job/69826632354

Eduard Zingerman (2):
  bpf: Fix u32/s32 bounds when ranges cross min/max boundary
  selftests/bpf: test refining u32/s32 bounds when ranges cross min/max
    boundary

Paul Chaignon (4):
  bpf: Improve bounds when s64 crosses sign boundary
  selftests/bpf: Test cross-sign 64bits range refinement
  selftests/bpf: Test invariants on JSLT crossing sign
  bpf: Add third round of bounds deduction

 kernel/bpf/verifier.c                         |  77 +++++++++
 .../selftests/bpf/prog_tests/reg_bounds.c     |  62 ++++++-
 .../selftests/bpf/progs/verifier_bounds.c     | 159 +++++++++++++++++-
 3 files changed, 292 insertions(+), 6 deletions(-)

-- 
2.43.0


WARNING: multiple messages have this Message-ID (diff)
From: Paul Chaignon <paul.chaignon@gmail.com>
To: stable@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Eduard Zingerman <eddyz87@gmail.com>,
	Alexei Starovoitov <ast@kernel.org>,
	Shung-Hsi Yu <shung-hsi.yu@suse.com>
Subject: [PATCH stable 6.12 0/6] bpf: Fix bounds when ranges cross sign boundary
Date: Sat, 4 Apr 2026 09:58:46 +0200	[thread overview]
Message-ID: <cover.1775206731.git.paul.chaignon@gmail.com> (raw)
Message-ID: <20260404075846.oQ1a29JAblx1zBWjJxdBR0_kLkrZhGk9eOYxxwzYXAo@z> (raw)

As discussed in [1], 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.

1: https://lore.kernel.org/stable/2026040240-friday-gurgling-7088@gregkh/
2: https://github.com/pchaigno/stable-bpf-ci/actions/runs/23940850516/job/69826632354

Eduard Zingerman (2):
  bpf: Fix u32/s32 bounds when ranges cross min/max boundary
  selftests/bpf: test refining u32/s32 bounds when ranges cross min/max
    boundary

Paul Chaignon (4):
  bpf: Improve bounds when s64 crosses sign boundary
  selftests/bpf: Test cross-sign 64bits range refinement
  selftests/bpf: Test invariants on JSLT crossing sign
  bpf: Add third round of bounds deduction

 kernel/bpf/verifier.c                         |  77 +++++++++
 .../selftests/bpf/prog_tests/reg_bounds.c     |  62 ++++++-
 .../selftests/bpf/progs/verifier_bounds.c     | 159 +++++++++++++++++-
 3 files changed, 292 insertions(+), 6 deletions(-)

-- 
2.43.0


             reply	other threads:[~2026-04-03 15:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-03 15:33 Paul Chaignon [this message]
2026-04-03 15:35 ` [PATCH stable 6.6 1/6] bpf: Improve bounds when s64 crosses sign boundary 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
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=cover.1775206731.git.paul.chaignon@gmail.com \
    --to=paul.chaignon@gmail.com \
    --cc=ast@kernel.org \
    --cc=eddyz87@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --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