From: Ard Biesheuvel <ardb@kernel.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: linux-efi <linux-efi@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH efi-next 2/3] efi/arm64: clean EFI stub exit code from cache instead of avoiding it
Date: Fri, 28 Feb 2020 12:21:09 +0100 [thread overview]
Message-ID: <CAKv+Gu-f5Bxv7C8yG1-bbQ5f0_e5W99nEiQYiXSOdr2+WJOHDg@mail.gmail.com> (raw)
In-Reply-To: <20200228111920.GB36089@lakrids.cambridge.arm.com>
On Fri, 28 Feb 2020 at 12:19, Mark Rutland <mark.rutland@arm.com> wrote:
>
> On Fri, Feb 28, 2020 at 11:14:50AM +0000, Mark Rutland wrote:
> > On Fri, Feb 28, 2020 at 11:02:43AM +0100, Ard Biesheuvel wrote:
> > > Commit 9f9223778 ("efi/libstub/arm: Make efi_entry() an ordinary PE/COFF
> > > entrypoint") modified the handover code written in assembler, and for
> > > maintainability, aligned the logic with the logic used in the 32-bit ARM
> > > version, which is to avoid cache maintenance on the remaining instructions
> > > in the subroutine that will be executed with the MMU and caches off, and
> > > instead, branch into the relocated copy of the kernel image.
> > >
> > > However, this assumes that this copy is executable, and this means we
> > > expect EFI_LOADER_DATA regions to be executable as well, which is not
> > > a reasonable assumption to make, even if this is true for most UEFI
> > > implementations today.
> > >
> > > So change this back, and add a __flush_dcache_area() call to cover the
> > > remaining code in the subroutine.
> > >
> > > Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
> > > ---
> > > arch/arm64/kernel/efi-entry.S | 18 +++++++++---------
> > > arch/arm64/kernel/image-vars.h | 2 +-
> > > 2 files changed, 10 insertions(+), 10 deletions(-)
> > >
> > > diff --git a/arch/arm64/kernel/efi-entry.S b/arch/arm64/kernel/efi-entry.S
> > > index 4cfd03c35c49..d5dee064975f 100644
> > > --- a/arch/arm64/kernel/efi-entry.S
> > > +++ b/arch/arm64/kernel/efi-entry.S
> > > @@ -19,7 +19,8 @@ ENTRY(efi_enter_kernel)
> > > * point stored in x0. Save those values in registers which are
> > > * callee preserved.
> > > */
> > > - mov x19, x0 // relocated Image address
> > > + ldr w2, =stext_offset
> > > + add x19, x0, x2 // relocated Image entrypoint
> > > mov x20, x1 // DTB address
> > >
> > > /*
> > > @@ -29,15 +30,14 @@ ENTRY(efi_enter_kernel)
> > > ldr w1, =kernel_size
> > > bl __flush_dcache_area
> > > ic ialluis
> > > - dsb sy
> > >
> > > /*
> > > - * Jump across, into the copy of the image that we just cleaned
> > > - * to the PoC, so that we can safely disable the MMU and caches.
> > > + * Flush the remainder of this routine to the PoC
> >
> > Minor nit, but could we please say 'Clean' rather than 'Flush' here?
> >
> > Even better, we now have __clean_dcache_area_poc(), and can use that
> > too.
>
> ... or if that's better as a subsequent cleanup for consistency, that'd
> also be fine, and needn't block this patch.
>
Thanks Mark. That sounds like a worthwhile improvement to fold in.
I'll need to add the __efistub_ alias for it, but I'm touching
image-vars.h in this patch anyway.
next prev parent reply other threads:[~2020-02-28 11:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 10:02 [PATCH efi-next 0/3] efi: assorted fixes Ard Biesheuvel
2020-02-28 10:02 ` [PATCH efi-next 1/3] efi/arm: clean EFI stub exit code from cache instead of avoiding it Ard Biesheuvel
2020-02-28 10:02 ` [PATCH efi-next 2/3] efi/arm64: " Ard Biesheuvel
2020-02-28 11:14 ` Mark Rutland
2020-02-28 11:19 ` Mark Rutland
2020-02-28 11:21 ` Ard Biesheuvel [this message]
2020-02-28 10:02 ` [PATCH efi-next 3/3] efi: mark all EFI runtime services as unsupported on non-EFI boot Ard Biesheuvel
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=CAKv+Gu-f5Bxv7C8yG1-bbQ5f0_e5W99nEiQYiXSOdr2+WJOHDg@mail.gmail.com \
--to=ardb@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=mark.rutland@arm.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;
as well as URLs for NNTP newsgroup(s).