From: Coiby Xu <coxu@redhat.com> To: Mimi Zohar <zohar@linux.ibm.com> Cc: kexec@lists.infradead.org, linux-arm-kernel@lists.infradead.org, Michal Suchanek <msuchanek@suse.de>, Baoquan He <bhe@redhat.com>, Dave Young <dyoung@redhat.com>, Will Deacon <will@kernel.org>, "Eric W . Biederman" <ebiederm@xmission.com>, Chun-Yi Lee <jlee@suse.com> Subject: Re: [PATCH v8 0/4] use more system keyrings to verify arm64 and s390 kexec kernel image signature Date: Thu, 16 Jun 2022 09:21:28 +0800 [thread overview] Message-ID: <20220616012128.7ufebi2lkusx5aga@Rk> (raw) In-Reply-To: <5b11a8043f78ef5ca41254b8a46f78dca0a5b159.camel@linux.ibm.com> Hi Mimi, On Thu, Jun 09, 2022 at 11:35:13AM -0400, Mimi Zohar wrote: >Hi Coiby, > >On Fri, 2022-05-27 at 21:43 +0800, Coiby Xu wrote: >> It seems I need to only change cover letter and commit message i.e. >> there is no concern about the code. So it's better to provide a >> new cover letter here to collect new feedback from you thus we >> can avoid unnecessary rounds of patch set. > >One other thing before re-posting, the existing Subject line is a bit >snarky. Perhaps you could come with a more appropriate title? How about "Using the same keyrings as x86 to verify kexec'ed kernel image signature for arm64 and s390" or "Uniform keyrings to verify kexec'ed kernel image signature across x86, arm64 and s390"? > >thanks, > >Mimi > -- Best regards, Coiby _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Coiby Xu <coxu@redhat.com> To: Mimi Zohar <zohar@linux.ibm.com> Cc: kexec@lists.infradead.org, linux-arm-kernel@lists.infradead.org, Michal Suchanek <msuchanek@suse.de>, Baoquan He <bhe@redhat.com>, Dave Young <dyoung@redhat.com>, Will Deacon <will@kernel.org>, "Eric W . Biederman" <ebiederm@xmission.com>, Chun-Yi Lee <jlee@suse.com> Subject: Re: [PATCH v8 0/4] use more system keyrings to verify arm64 and s390 kexec kernel image signature Date: Thu, 16 Jun 2022 09:21:28 +0800 [thread overview] Message-ID: <20220616012128.7ufebi2lkusx5aga@Rk> (raw) In-Reply-To: <5b11a8043f78ef5ca41254b8a46f78dca0a5b159.camel@linux.ibm.com> Hi Mimi, On Thu, Jun 09, 2022 at 11:35:13AM -0400, Mimi Zohar wrote: >Hi Coiby, > >On Fri, 2022-05-27 at 21:43 +0800, Coiby Xu wrote: >> It seems I need to only change cover letter and commit message i.e. >> there is no concern about the code. So it's better to provide a >> new cover letter here to collect new feedback from you thus we >> can avoid unnecessary rounds of patch set. > >One other thing before re-posting, the existing Subject line is a bit >snarky. Perhaps you could come with a more appropriate title? How about "Using the same keyrings as x86 to verify kexec'ed kernel image signature for arm64 and s390" or "Uniform keyrings to verify kexec'ed kernel image signature across x86, arm64 and s390"? > >thanks, > >Mimi > -- Best regards, Coiby _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-06-16 1:25 UTC|newest] Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-12 7:01 [PATCH v8 0/4] use more system keyrings to verify arm64 and s390 kexec kernel image signature Coiby Xu 2022-05-12 7:01 ` Coiby Xu 2022-05-12 7:01 ` [PATCH v8 1/4] kexec: clean up arch_kexec_kernel_verify_sig Coiby Xu 2022-05-12 7:01 ` Coiby Xu 2022-05-12 7:01 ` Coiby Xu 2022-06-09 21:57 ` Mimi Zohar 2022-06-09 21:57 ` Mimi Zohar 2022-06-09 21:57 ` Mimi Zohar 2022-05-12 7:01 ` [PATCH v8 2/4] kexec, KEYS: make the code in bzImage64_verify_sig generic Coiby Xu 2022-05-12 7:01 ` Coiby Xu 2022-05-12 7:01 ` Coiby Xu 2022-05-12 7:21 ` Baoquan He 2022-05-12 7:21 ` Baoquan He 2022-05-12 7:21 ` Baoquan He 2022-06-09 22:18 ` Mimi Zohar 2022-06-09 22:18 ` Mimi Zohar 2022-06-09 22:18 ` Mimi Zohar 2022-06-16 1:47 ` Coiby Xu 2022-06-16 1:47 ` Coiby Xu 2022-06-16 1:47 ` Coiby Xu 2022-05-12 7:01 ` [PATCH v8 3/4] arm64: kexec_file: use more system keyrings to verify kernel image signature Coiby Xu 2022-05-12 7:01 ` Coiby Xu 2022-05-12 7:01 ` Coiby Xu 2022-06-09 23:15 ` Mimi Zohar 2022-06-09 23:15 ` Mimi Zohar 2022-06-09 23:15 ` Mimi Zohar 2022-06-16 1:22 ` Coiby Xu 2022-06-16 1:22 ` Coiby Xu 2022-06-16 1:22 ` Coiby Xu 2022-06-17 9:34 ` Michal Suchánek 2022-06-17 9:34 ` Michal Suchánek 2022-06-17 9:34 ` Michal Suchánek 2022-05-12 7:01 ` [PATCH v8 4/4] kexec, KEYS, s390: Make use of built-in and secondary keyring for signature verification Coiby Xu 2022-05-12 7:01 ` Coiby Xu 2022-05-12 7:01 ` Coiby Xu 2022-05-18 11:29 ` Heiko Carstens 2022-05-18 11:29 ` Heiko Carstens 2022-05-18 11:29 ` Heiko Carstens 2022-05-19 0:39 ` Baoquan He 2022-05-19 0:39 ` Baoquan He 2022-05-19 0:39 ` Baoquan He 2022-05-19 11:56 ` Mimi Zohar 2022-05-19 11:56 ` Mimi Zohar 2022-05-19 11:56 ` Mimi Zohar 2022-05-19 14:22 ` Baoquan He 2022-05-19 14:22 ` Baoquan He 2022-05-19 14:22 ` Baoquan He 2022-05-19 17:11 ` Michal Suchánek 2022-05-19 17:11 ` Michal =?unknown-8bit?q?Such=C3=A1nek?= 2022-05-19 17:11 ` Michal Suchánek 2022-06-16 1:46 ` Coiby Xu 2022-06-16 1:46 ` Coiby Xu 2022-06-16 1:46 ` Coiby Xu 2022-05-20 17:04 ` [PATCH v8 0/4] use more system keyrings to verify arm64 and s390 kexec kernel image signature Mimi Zohar 2022-05-20 17:04 ` Mimi Zohar 2022-05-25 9:59 ` Coiby Xu 2022-05-25 9:59 ` Coiby Xu 2022-05-25 13:30 ` Mimi Zohar 2022-05-25 13:30 ` Mimi Zohar 2022-05-27 13:43 ` Coiby Xu 2022-05-27 13:43 ` Coiby Xu 2022-05-27 16:45 ` Mimi Zohar 2022-05-27 16:45 ` Mimi Zohar 2022-06-16 1:15 ` Coiby Xu 2022-06-16 1:15 ` Coiby Xu 2022-06-17 3:57 ` Coiby Xu 2022-06-17 3:57 ` Coiby Xu 2022-06-17 11:58 ` Mimi Zohar 2022-06-17 11:58 ` Mimi Zohar 2022-06-20 13:14 ` Coiby Xu 2022-06-20 13:14 ` Coiby Xu 2022-06-09 15:35 ` Mimi Zohar 2022-06-09 15:35 ` Mimi Zohar 2022-06-16 1:21 ` Coiby Xu [this message] 2022-06-16 1:21 ` Coiby Xu 2022-06-17 12:06 ` Mimi Zohar 2022-06-17 12:06 ` Mimi Zohar
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=20220616012128.7ufebi2lkusx5aga@Rk \ --to=coxu@redhat.com \ --cc=bhe@redhat.com \ --cc=dyoung@redhat.com \ --cc=ebiederm@xmission.com \ --cc=jlee@suse.com \ --cc=kexec@lists.infradead.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=msuchanek@suse.de \ --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: linkBe 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.