All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Shung-Hsi Yu <shung-hsi.yu@suse.com>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Alexei Starovoitov <ast@kernel.org>,
	Eduard Zingerman <eddyz87@gmail.com>,
	Andrii Nakryiko <andrii@kernel.org>, Tao Lyu <tao.lyu@epfl.ch>,
	Levi Zim <rsworktech@outlook.com>,
	Paul Chaignon <paul.chaignon@gmail.com>
Subject: Re: [PATCH 6.6.y 00/10] bpf: fix precision backtracking instruction iteration
Date: Mon, 11 May 2026 20:17:53 -0400	[thread overview]
Message-ID: <20260511220000.stable-reply-item002@kernel.org> (raw)
In-Reply-To: <cover.1778516196.git.paul.chaignon@gmail.com>

On Mon, May 11, 2026 at 06:21:22PM +0200, Paul Chaignon wrote:
> This patchset backports commit 41f6f64e6999 ("bpf: support non-r10
> register spill/fill to/from stack in precision tracking") again, but
> this time with the subsequent commits that improved the efficiency of
> the verifier. In addition, the last two commits fix and test a
> regression that was later found in commit 41f6f64e6999.

Queued for 6.6, thanks.

I also separately picked up 69772f509e08 ("bpf: Don't mark STACK_INVALID
as STACK_MISC in mark_stack_slot_misc") as a follow-up to patch 3/10
(eaf18febd6eb).

-- 
Thanks,
Sasha

  parent reply	other threads:[~2026-05-12  0:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-11 16:21 [PATCH 6.6.y 00/10] bpf: fix precision backtracking instruction iteration Paul Chaignon
2026-05-11 16:22 ` [PATCH 6.6.y 01/10] bpf: support non-r10 register spill/fill to/from stack in precision tracking Paul Chaignon
2026-05-11 16:23 ` [PATCH 6.6.y 02/10] selftests/bpf: add stack access precision test Paul Chaignon
2026-05-11 16:23 ` [PATCH 6.6.y 03/10] bpf: preserve STACK_ZERO slots on partial reg spills Paul Chaignon
2026-05-11 16:24 ` [PATCH 6.6.y 04/10] selftests/bpf: validate STACK_ZERO is preserved on subreg spill Paul Chaignon
2026-05-11 16:24 ` [PATCH 6.6.y 05/10] bpf: preserve constant zero when doing partial register restore Paul Chaignon
2026-05-11 16:24 ` [PATCH 6.6.y 06/10] selftests/bpf: validate zero preservation for sub-slot loads Paul Chaignon
2026-05-11 16:24 ` [PATCH 6.6.y 07/10] bpf: track aligned STACK_ZERO cases as imprecise spilled registers Paul Chaignon
2026-05-11 16:24 ` [PATCH 6.6.y 08/10] selftests/bpf: validate precision logic in partial_stack_load_preserves_zeros Paul Chaignon
2026-05-11 16:25 ` [PATCH 6.6.y 09/10] bpf: handle fake register spill to stack with BPF_ST_MEM instruction Paul Chaignon
2026-05-11 16:25 ` [PATCH 6.6.y 10/10] selftests/bpf: validate fake register spill/fill precision backtracking logic Paul Chaignon
2026-05-12  0:17 ` Sasha Levin [this message]
2026-05-12 12:01   ` [PATCH 6.6.y 00/10] bpf: fix precision backtracking instruction iteration Paul Chaignon
2026-05-12  6:51 ` Levi Zim

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=20260511220000.stable-reply-item002@kernel.org \
    --to=sashal@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=paul.chaignon@gmail.com \
    --cc=rsworktech@outlook.com \
    --cc=shung-hsi.yu@suse.com \
    --cc=stable@vger.kernel.org \
    --cc=tao.lyu@epfl.ch \
    /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.