From: Lee Jones <lee@kernel.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: linux-efi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
will@kernel.org, catalin.marinas@arm.com,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH v3 0/2] efi: Follow-up fixes for EFI runtime stack
Date: Mon, 9 Jan 2023 10:38:25 +0000 [thread overview]
Message-ID: <Y7vuobjqmoyT+MPB@google.com> (raw)
In-Reply-To: <20230106174703.1883495-1-ardb@kernel.org>
On Fri, 06 Jan 2023, Ard Biesheuvel wrote:
> Commit ff7a167961d1b ("arm64: efi: Execute runtime services from a
> dedicated stack") introduced a dedicated stack for EFI runtime services,
> in an attempt to make the execution of EFI runtime services more robust,
> given that they execute at the same privilege level as the kernel.
>
> However, this stack needs to be declared to the stacktrace machinery,
> which is careful not to walk the stack when it leads into memory regions
> that are not known to be allocated for stack use.
>
> Also, given that the ACPI code may invoke the low-level EFI runtime call
> wrapper without using the dedicated kernel thread and workqueue, we
> should take this into account when trying to gracefully handle
> synchronous exceptions.
>
> Changes since v2:
> - clear efi_rt_stack_top[-1] from asm code, and use READ_ONCE() to read
> its value when not holding the spinlock, to ensure that all accesses
> are safe under concurrency;
> - add Mark's ack to patch #2
>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Cc: Lee Jones <lee@kernel.org>
>
> Ard Biesheuvel (2):
> arm64: efi: Avoid workqueue to check whether EFI runtime is live
> arm64: efi: Account for the EFI runtime stack in stack unwinder
Should either / both of these be routed to Stable?
If so, we should probably Cc: them.
> arch/arm64/include/asm/efi.h | 9 +++++++++
> arch/arm64/include/asm/stacktrace.h | 15 +++++++++++++++
> arch/arm64/kernel/efi-rt-wrapper.S | 6 ++++++
> arch/arm64/kernel/efi.c | 3 ++-
> arch/arm64/kernel/stacktrace.c | 12 ++++++++++++
> 5 files changed, 44 insertions(+), 1 deletion(-)
>
> --
> 2.39.0
>
--
Lee Jones [李琼斯]
WARNING: multiple messages have this Message-ID (diff)
From: Lee Jones <lee@kernel.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: linux-efi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
will@kernel.org, catalin.marinas@arm.com,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH v3 0/2] efi: Follow-up fixes for EFI runtime stack
Date: Mon, 9 Jan 2023 10:38:25 +0000 [thread overview]
Message-ID: <Y7vuobjqmoyT+MPB@google.com> (raw)
In-Reply-To: <20230106174703.1883495-1-ardb@kernel.org>
On Fri, 06 Jan 2023, Ard Biesheuvel wrote:
> Commit ff7a167961d1b ("arm64: efi: Execute runtime services from a
> dedicated stack") introduced a dedicated stack for EFI runtime services,
> in an attempt to make the execution of EFI runtime services more robust,
> given that they execute at the same privilege level as the kernel.
>
> However, this stack needs to be declared to the stacktrace machinery,
> which is careful not to walk the stack when it leads into memory regions
> that are not known to be allocated for stack use.
>
> Also, given that the ACPI code may invoke the low-level EFI runtime call
> wrapper without using the dedicated kernel thread and workqueue, we
> should take this into account when trying to gracefully handle
> synchronous exceptions.
>
> Changes since v2:
> - clear efi_rt_stack_top[-1] from asm code, and use READ_ONCE() to read
> its value when not holding the spinlock, to ensure that all accesses
> are safe under concurrency;
> - add Mark's ack to patch #2
>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Cc: Lee Jones <lee@kernel.org>
>
> Ard Biesheuvel (2):
> arm64: efi: Avoid workqueue to check whether EFI runtime is live
> arm64: efi: Account for the EFI runtime stack in stack unwinder
Should either / both of these be routed to Stable?
If so, we should probably Cc: them.
> arch/arm64/include/asm/efi.h | 9 +++++++++
> arch/arm64/include/asm/stacktrace.h | 15 +++++++++++++++
> arch/arm64/kernel/efi-rt-wrapper.S | 6 ++++++
> arch/arm64/kernel/efi.c | 3 ++-
> arch/arm64/kernel/stacktrace.c | 12 ++++++++++++
> 5 files changed, 44 insertions(+), 1 deletion(-)
>
> --
> 2.39.0
>
--
Lee Jones [李琼斯]
_______________________________________________
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:[~2023-01-09 10:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 17:47 [PATCH v3 0/2] efi: Follow-up fixes for EFI runtime stack Ard Biesheuvel
2023-01-06 17:47 ` Ard Biesheuvel
2023-01-06 17:47 ` [PATCH v3 1/2] arm64: efi: Avoid workqueue to check whether EFI runtime is live Ard Biesheuvel
2023-01-06 17:47 ` Ard Biesheuvel
2023-01-09 13:26 ` Mark Rutland
2023-01-09 13:26 ` Mark Rutland
2023-01-06 17:47 ` [PATCH v3 2/2] arm64: efi: Account for the EFI runtime stack in stack unwinder Ard Biesheuvel
2023-01-06 17:47 ` Ard Biesheuvel
2023-01-10 20:48 ` Nathan Chancellor
2023-01-10 20:48 ` Nathan Chancellor
2023-01-11 8:45 ` Ard Biesheuvel
2023-01-11 8:45 ` Ard Biesheuvel
2023-01-11 21:18 ` Nathan Chancellor
2023-01-11 21:18 ` Nathan Chancellor
2023-01-11 22:53 ` Ard Biesheuvel
2023-01-11 22:53 ` Ard Biesheuvel
2023-01-09 10:38 ` Lee Jones [this message]
2023-01-09 10:38 ` [PATCH v3 0/2] efi: Follow-up fixes for EFI runtime stack Lee Jones
2023-01-09 13:46 ` Ard Biesheuvel
2023-01-09 13:46 ` 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=Y7vuobjqmoyT+MPB@google.com \
--to=lee@kernel.org \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=mark.rutland@arm.com \
--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 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.