From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: haixiao.yan.cn@eng.windriver.com, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH] powerpc/rtas: Prevent Spectre v1 gadget construction in sys_rtas()
Date: Fri, 13 Dec 2024 10:13:25 -0500 [thread overview]
Message-ID: <20241213092118-fe9f63a978baa269@stable.kernel.org> (raw)
In-Reply-To: <20241213034422.2916981-1-haixiao.yan.cn@eng.windriver.com>
[ Sasha's backport helper bot ]
Hi,
The upstream commit SHA1 provided is correct: 0974d03eb479384466d828d65637814bee6b26d7
WARNING: Author mismatch between patch and upstream commit:
Backport author: haixiao.yan.cn@eng.windriver.com
Commit author: Nathan Lynch <nathanl@linux.ibm.com>
Status in newer kernel trees:
6.12.y | Present (exact SHA1)
Note: The patch differs from the upstream commit:
---
Failed to apply patch cleanly, falling back to interdiff...
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.12.y | Failed | N/A |
| stable/linux-6.6.y | Failed | N/A |
| stable/linux-6.1.y | Success | Success |
| stable/linux-5.15.y | Success | Success |
| stable/linux-5.10.y | Success | Success |
| stable/linux-5.4.y | Success | Success |
next prev parent reply other threads:[~2024-12-13 15:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 3:44 [PATCH] powerpc/rtas: Prevent Spectre v1 gadget construction in sys_rtas() haixiao.yan.cn
2024-12-13 11:14 ` Greg KH
2024-12-13 11:15 ` Greg KH
2024-12-13 15:13 ` Sasha Levin [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-31 0:44 Nathan Lynch
2024-05-31 0:44 ` Nathan Lynch via B4 Relay
2024-05-31 13:45 ` Breno Leitao
2024-05-31 16:45 ` Nathan Lynch
2024-05-31 17:20 ` Breno Leitao
2024-07-06 23:10 ` Michael Ellerman
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=20241213092118-fe9f63a978baa269@stable.kernel.org \
--to=sashal@kernel.org \
--cc=haixiao.yan.cn@eng.windriver.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 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.