From: Greg KH <gregkh@linuxfoundation.org>
To: Lee Jones <lee@kernel.org>
Cc: Ard Biesheuvel <ardb@kernel.org>,
stable@vger.kernel.org, linux-efi@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, will@kernel.org,
catalin.marinas@arm.com, mark.rutland@arm.com,
Sami Tolvanen <samitolvanen@google.com>,
Kees Cook <keescook@chromium.org>
Subject: Re: [PATCH 1/2] arm64: efi: Execute runtime services from a dedicated stack
Date: Wed, 4 Jan 2023 15:52:03 +0100 [thread overview]
Message-ID: <Y7WSk1q1aTkWlsQ9@kroah.com> (raw)
In-Reply-To: <Y7WQVreh3l9hYarK@google.com>
On Wed, Jan 04, 2023 at 02:42:30PM +0000, Lee Jones wrote:
> On Wed, 04 Jan 2023, Ard Biesheuvel wrote:
>
> > On Wed, 4 Jan 2023 at 11:40, Lee Jones <lee@kernel.org> wrote:
> > >
> > > On Mon, 05 Dec 2022, Ard Biesheuvel wrote:
> > >
> > > > With the introduction of PRMT in the ACPI subsystem, the EFI rts
> > > > workqueue is no longer the only caller of efi_call_virt_pointer() in the
> > > > kernel. This means the EFI runtime services lock is no longer sufficient
> > > > to manage concurrent calls into firmware, but also that firmware calls
> > > > may occur that are not marshalled via the workqueue mechanism, but
> > > > originate directly from the caller context.
> > > >
> > > > For added robustness, and to ensure that the runtime services have 8 KiB
> > > > of stack space available as per the EFI spec, introduce a spinlock
> > > > protected EFI runtime stack of 8 KiB, where the spinlock also ensures
> > > > serialization between the EFI rts workqueue (which itself serializes EFI
> > > > runtime calls) and other callers of efi_call_virt_pointer().
> > > >
> > > > While at it, use the stack pivot to avoid reloading the shadow call
> > > > stack pointer from the ordinary stack, as doing so could produce a
> > > > gadget to defeat it.
> > > >
> > > > Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
> > > > ---
> > > > arch/arm64/include/asm/efi.h | 3 +++
> > > > arch/arm64/kernel/efi-rt-wrapper.S | 13 +++++++++-
> > > > arch/arm64/kernel/efi.c | 25 ++++++++++++++++++++
> > > > 3 files changed, 40 insertions(+), 1 deletion(-)
> > >
> > > Could we have this in Stable please?
> > >
> > > Upstream commit: ff7a167961d1b ("arm64: efi: Execute runtime services from a dedicated stack")
> > >
> > > Ard, do we need Patch 2 as well, or can this be applied on its own?
> > >
> >
> > Thanks for the reminder.
> >
> > Only patch #1 is needed. It should be applied to v5.10 and later.
>
> Perfect, thanks Ard.
Now queued up, thanks.
greg k-h
next prev parent reply other threads:[~2023-01-04 14:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221205201210.463781-1-ardb@kernel.org>
[not found] ` <20221205201210.463781-2-ardb@kernel.org>
2023-01-04 10:40 ` [PATCH 1/2] arm64: efi: Execute runtime services from a dedicated stack Lee Jones
2023-01-04 13:56 ` Ard Biesheuvel
2023-01-04 14:42 ` Lee Jones
2023-01-04 14:52 ` Greg KH [this message]
2023-01-04 16:13 ` Mark Rutland
2023-01-04 16:15 ` Ard Biesheuvel
2023-01-04 16:30 ` Mark Rutland
2023-01-04 16:32 ` Ard Biesheuvel
2023-01-05 11:13 ` Greg KH
2023-01-17 16:56 ` Lee Jones
2023-01-22 13:48 ` Greg KH
2025-03-09 10:14 ` SDL
2023-01-05 12:56 ` Mark Rutland
2023-01-05 13:37 ` 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=Y7WSk1q1aTkWlsQ9@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=keescook@chromium.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=samitolvanen@google.com \
--cc=stable@vger.kernel.org \
--cc=will@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