From: Greg KH <gregkh@linuxfoundation.org>
To: Shung-Hsi Yu <shung-hsi.yu@suse.com>
Cc: stable@vger.kernel.org, Sasha Levin <sashal@kernel.org>,
bpf@vger.kernel.org, Yonghong Song <yonghong.song@linux.dev>,
Alexei Starovoitov <ast@kernel.org>
Subject: Re: [PATCH stable 6.10 2/2] selftests/bpf: Add a test to verify previous stacksafe() fix
Date: Tue, 27 Aug 2024 14:25:16 +0200 [thread overview]
Message-ID: <2024082706-strongbox-driving-46c5@gregkh> (raw)
In-Reply-To: <20240823014631.114866-2-shung-hsi.yu@suse.com>
On Fri, Aug 23, 2024 at 09:46:31AM +0800, Shung-Hsi Yu wrote:
> From: Yonghong Song <yonghong.song@linux.dev>
>
> [ Upstream commit 662c3e2db00f92e50c26e9dc4fe47c52223d9982 ]
>
> A selftest is added such that without the previous patch,
> a crash can happen. With the previous patch, the test can
> run successfully. The new test is written in a way which
> mimics original crash case:
> main_prog
> static_prog_1
> static_prog_2
> where static_prog_1 has different paths to static_prog_2
> and some path has stack allocated and some other path
> does not. A stacksafe() checking in static_prog_2()
> triggered the crash.
>
> Signed-off-by: Yonghong Song <yonghong.song@linux.dev>
> Link: https://lore.kernel.org/r/20240812214852.214037-1-yonghong.song@linux.dev
> Signed-off-by: Alexei Starovoitov <ast@kernel.org>
> Signed-off-by: Shung-Hsi Yu <shung-hsi.yu@suse.com>
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2024-08-27 12:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-23 1:46 [PATCH stable 6.10 1/2] bpf: Fix a kernel verifier crash in stacksafe() Shung-Hsi Yu
2024-08-23 1:46 ` [PATCH stable 6.10 2/2] selftests/bpf: Add a test to verify previous stacksafe() fix Shung-Hsi Yu
2024-08-27 12:25 ` Greg KH [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=2024082706-strongbox-driving-46c5@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=shung-hsi.yu@suse.com \
--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