From: Mimi Zohar <zohar@linux.ibm.com>
To: Heiko Carstens <hca@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>
Cc: Jarkko Sakkinen <jarkko@kernel.org>,
Vasily Gorbik <gor@linux.ibm.com>,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
linux-integrity@vger.kernel.org
Subject: Re: [PATCH v2] s390/ipl: fix virtual vs physical address confusion
Date: Wed, 16 Aug 2023 13:34:55 -0400 [thread overview]
Message-ID: <47dd1902aa6c2328680223beb1235b28a36f6193.camel@linux.ibm.com> (raw)
In-Reply-To: <20230816154419.29011-A-hca@linux.ibm.com>
On Wed, 2023-08-16 at 17:44 +0200, Heiko Carstens wrote:
> On Wed, Aug 16, 2023 at 03:29:42PM +0200, Alexander Gordeev wrote:
> > The value of ipl_cert_list_addr boot variable contains
> > a physical address, which is used directly. That works
> > because virtual and physical address spaces are currently
> > the same, but otherwise it is wrong.
> >
> > While at it, fix also a comment for the platform keyring.
> >
> > Signed-off-by: Alexander Gordeev <agordeev@linux.ibm.com>
> > ---
> > arch/s390/kernel/machine_kexec_file.c | 4 ++--
> > arch/s390/kernel/setup.c | 2 +-
> > security/integrity/platform_certs/load_ipl_s390.c | 4 ++--
> > 3 files changed, 5 insertions(+), 5 deletions(-)
>
> Mimi, Jarkko, any objections from your side?
> I would take this via the s390 tree.
No objections from my side.
--
thanks,
Mimi
next prev parent reply other threads:[~2023-08-16 18:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 13:29 [PATCH v2] s390/ipl: fix virtual vs physical address confusion Alexander Gordeev
2023-08-16 15:44 ` Heiko Carstens
2023-08-16 17:34 ` Mimi Zohar [this message]
2023-08-16 19:32 ` Jarkko Sakkinen
2023-08-16 16:13 ` Mimi Zohar
2023-08-16 17:07 ` Alexander Gordeev
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=47dd1902aa6c2328680223beb1235b28a36f6193.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=jarkko@kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@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