From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Chen Linxuan <chenlinxuan@deepin.org>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH stable 6.6] lib/buildid: Handle memfd_secret() files in build_id_parse()
Date: Fri, 14 Mar 2025 19:10:15 -0400 [thread overview]
Message-ID: <20250314083811-82152b90557ac49c@stable.kernel.org> (raw)
In-Reply-To: <0D63CE7960D94BE9+20250314090337.31408-2-chenlinxuan@deepin.org>
[ Sasha's backport helper bot ]
Hi,
✅ All tests passed successfully. No issues detected.
No action required from the submitter.
The upstream commit SHA1 provided is correct: 5ac9b4e935dfc6af41eee2ddc21deb5c36507a9f
WARNING: Author mismatch between patch and upstream commit:
Backport author: Chen Linxuan<chenlinxuan@deepin.org>
Commit author: Andrii Nakryiko<andrii@kernel.org>
Status in newer kernel trees:
6.13.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
Note: The patch differs from the upstream commit:
---
1: 5ac9b4e935dfc < -: ------------- lib/buildid: Handle memfd_secret() files in build_id_parse()
-: ------------- > 1: 251f716878081 lib/buildid: Handle memfd_secret() files in build_id_parse()
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.6.y | Success | Success |
next prev parent reply other threads:[~2025-03-14 23:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 9:03 [PATCH stable 6.6] lib/buildid: Handle memfd_secret() files in build_id_parse() Chen Linxuan
2025-03-14 23:10 ` Sasha Levin [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-11 10:05 Chen Linxuan
2025-03-11 11:14 ` Greg KH
2025-03-12 3:03 ` Chen Linxuan
2025-03-12 18:43 ` Andrii Nakryiko
2025-03-13 16:04 ` Greg KH
2025-03-13 9:01 ` Sasha Levin
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=20250314083811-82152b90557ac49c@stable.kernel.org \
--to=sashal@kernel.org \
--cc=chenlinxuan@deepin.org \
--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