From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>, Shung-Hsi Yu <shung-hsi.yu@suse.com>
Subject: Re: [PATCH stable 6.18 0/6] bpf: verifier: linked register tests and fixes
Date: Sun, 19 Jul 2026 11:00:22 -0400 [thread overview]
Message-ID: <20260718192718.0008-stable-reply@kernel.org> (raw)
In-Reply-To: <20260717044731.121353-1-shung-hsi.yu@suse.com>
> This patchset mainly aims to backport upstream commit 1b327732c846
> ("bpf: Clear delta when clearing reg id for non-{add,sub} ops") (patch
> 4), and its selftests patch in commit cac16ce1e378 ("selftests/bpf: Add
> tests for stale delta leaking through id reassignment") (patch 6).
Queued the series for 6.18, thanks.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-07-19 15:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 4:47 [PATCH stable 6.18 0/6] bpf: verifier: linked register tests and fixes Shung-Hsi Yu
2026-07-17 4:47 ` [PATCH stable 6.18 1/6] selftests: bpf: Add test for multiple syncs from linked register Shung-Hsi Yu
2026-07-17 4:47 ` [PATCH stable 6.18 2/6] selftests/bpf: Add tests for improved linked register tracking Shung-Hsi Yu
2026-07-17 4:47 ` [PATCH stable 6.18 3/6] selftests/bpf: Add a test cases for sync_linked_regs regarding zext propagation Shung-Hsi Yu
2026-07-17 4:47 ` [PATCH stable 6.18 4/6] bpf: Clear delta when clearing reg id for non-{add,sub} ops Shung-Hsi Yu
2026-07-17 4:47 ` [PATCH stable 6.18 5/6] selftests/bpf: Add tests for delta tracking when src_reg == dst_reg Shung-Hsi Yu
2026-07-17 4:47 ` [PATCH stable 6.18 6/6] selftests/bpf: Add tests for stale delta leaking through id reassignment Shung-Hsi Yu
2026-07-19 15:00 ` Sasha Levin [this message]
2026-07-21 6:45 ` [PATCH stable 6.18 0/6] bpf: verifier: linked register tests and fixes Shung-Hsi Yu
2026-07-21 8:03 ` Shung-Hsi Yu
2026-07-21 10:18 ` Greg KH
2026-07-23 2:42 ` Shung-Hsi Yu
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=20260718192718.0008-stable-reply@kernel.org \
--to=sashal@kernel.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