From: Philo Lu <lulie@linux.alibaba.com>
To: Sasha Levin <sashal@kernel.org>, stable@vger.kernel.org
Cc: daniel@iogearbox.net, info@starlabs.sg, ast@kernel.org,
john.fastabend@gmail.com, andrii@kernel.org,
martin.lau@linux.dev, song@kernel.org, yonghong.song@linux.dev,
kpsingh@kernel.org, sdf@google.com, haoluo@google.com,
jolsa@kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, mykolal@fb.com, shuah@kernel.org,
linux-kselftest@vger.kernel.org, dust.li@linux.alibaba.com
Subject: Re: [PATCH 6.6.y/6.12.y/6.18.y 0/2] bpf: Fix ld_{abs,ind} failure path analysis in subprogs
Date: Tue, 28 Jul 2026 18:43:51 +0800 [thread overview]
Message-ID: <74589286-d967-4fc1-b044-1f9b2376c94a@linux.alibaba.com> (raw)
In-Reply-To: <20260724105500.stable-0001@kernel.org>
On 7/24/26 7:22 PM, Sasha Levin wrote:
> One follow-up: the Fixes commit 09b28d76eac4 ("bpf: Add abnormal return
> checks.") is also present in 6.1, 5.15 and 5.10, and the fix is absent there,
> so those trees are affected as well but were not covered by this submission.
> They likely need a further adaptation. Could you extend coverage with adapted
> backports for 6.1/5.15/5.10?
>
I've posted patches for 6.1/5.15/5.10. The 6.1 one is identical;
5.10/5.15 required minor adaptation.
The selftests patch can't go into any of the three trees due to missing
dependencies.
Thanks.
--
Philo
prev parent reply other threads:[~2026-07-28 10:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 7:39 Philo Lu
2026-07-22 7:39 ` [PATCH 6.6.y/6.12.y/6.18.y 1/2] " Philo Lu
2026-07-22 8:49 ` Pu Lehui
2026-07-22 7:39 ` [PATCH 6.6.y/6.12.y/6.18.y 2/2] selftests/bpf: Add tests for ld_{abs,ind} failure path " Philo Lu
2026-07-22 8:50 ` Pu Lehui
2026-07-24 11:22 ` [PATCH 6.6.y/6.12.y/6.18.y 0/2] bpf: Fix ld_{abs,ind} failure path analysis " Sasha Levin
2026-07-28 10:43 ` Philo Lu [this message]
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=74589286-d967-4fc1-b044-1f9b2376c94a@linux.alibaba.com \
--to=lulie@linux.alibaba.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dust.li@linux.alibaba.com \
--cc=haoluo@google.com \
--cc=info@starlabs.sg \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mykolal@fb.com \
--cc=sashal@kernel.org \
--cc=sdf@google.com \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=stable@vger.kernel.org \
--cc=yonghong.song@linux.dev \
/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
all inboxes | Powered by JetHome®