From: Greg KH <gregkh@linuxfoundation.org>
To: Coiby Xu <coxu@redhat.com>
Cc: bhe@redhat.com, msuchanek@suse.de, will@kernel.org,
zohar@linux.ibm.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] arm64: kexec_file: use more system keyrings to verify kernel" failed to apply to 5.18-stable tree
Date: Fri, 19 Aug 2022 16:43:33 +0200 [thread overview]
Message-ID: <Yv+hlUo+42ldU5pD@kroah.com> (raw)
In-Reply-To: <20220818041906.dgj4eqrpropved4e@Rk>
On Thu, Aug 18, 2022 at 12:19:06PM +0800, Coiby Xu wrote:
> Hi Greg,
>
> This patch depends on three prerequisites but 5.18-stable tree has two
> prerequisites backported. So the full list of commit ids should be
> backported is shown below,
> 1. c903dae8941d ("kexec, KEYS: make the code in bzImage64_verify_sig generic")
> 2. 0d519cadf751 ("arm64: kexec_file: use more system keyrings to verify kernel image signature")
>
> $ git checkout -b arm_key_5.18.y stable/linux-5.18.y Updating
> files: 100% (43489/43489), done.
> branch 'arm_key_5.18.y' set up to track 'stable/linux-5.18.y'.
> Switched to a new branch 'arm_key_5.18.y'
>
> $ git cherry-pick c903dae8941d 0d519cadf751 Auto-merging
> include/linux/kexec.h
> Auto-merging kernel/kexec_file.c
> [arm_key_5.18.y f3c9c5542700] kexec, KEYS: make the code in bzImage64_verify_sig generic
> Date: Thu Jul 14 21:40:25 2022 +0800
> 3 files changed, 25 insertions(+), 19 deletions(-)
> [arm_key_5.18.y 532854860941] arm64: kexec_file: use more system keyrings to verify kernel image signature
> Date: Thu Jul 14 21:40:26 2022 +0800
> 1 file changed, 1 insertion(+), 10 deletions(-)
Both now queued up, thanks.
greg k-h
prev parent reply other threads:[~2022-08-19 14:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 15:33 FAILED: patch "[PATCH] arm64: kexec_file: use more system keyrings to verify kernel" failed to apply to 5.18-stable tree gregkh
2022-08-18 4:19 ` Coiby Xu
2022-08-19 14:43 ` 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=Yv+hlUo+42ldU5pD@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bhe@redhat.com \
--cc=coxu@redhat.com \
--cc=msuchanek@suse.de \
--cc=stable@vger.kernel.org \
--cc=will@kernel.org \
--cc=zohar@linux.ibm.com \
/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