From: Ard Biesheuvel <ardb@kernel.org>
To: linux-arm-kernel@lists.infradead.org
Cc: linux-acpi@vger.kernel.org, will@kernel.org,
catalin.marinas@arm.com, lorenzo.pieralisi@arm.com,
sudeep.holla@arm.com, kernel-hardening@lists.openwall.com,
Ard Biesheuvel <ardb@kernel.org>
Subject: [PATCH v3 0/2] arm64/acpi: restrict AML opregion memory access
Date: Fri, 26 Jun 2020 17:58:30 +0200 [thread overview]
Message-ID: <20200626155832.2323789-1-ardb@kernel.org> (raw)
v2:
- do a more elaborate check on the region, against the EFI memory map
v3:
- split into two patches
- fallback to __ioremap() for ACPI reclaim memory, in case it is not covered
by the linear mapping (e.g., when booting a kdump kernel)
Ard Biesheuvel (2):
arm64/acpi: disallow AML memory opregions to access kernel memory
arm64/acpi: disallow writeable AML opregion mapping for EFI code
regions
arch/arm64/include/asm/acpi.h | 15 +---
arch/arm64/kernel/acpi.c | 75 ++++++++++++++++++++
2 files changed, 76 insertions(+), 14 deletions(-)
--
2.27.0
next reply other threads:[~2020-06-26 15:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-26 15:58 Ard Biesheuvel [this message]
2020-06-26 15:58 ` [PATCH v3 1/2] arm64/acpi: disallow AML memory opregions to access kernel memory Ard Biesheuvel
2020-09-28 16:02 ` Jonathan Cameron
2020-09-28 16:49 ` Ard Biesheuvel
2020-09-28 17:17 ` Jonathan Cameron
2020-09-29 9:29 ` Ard Biesheuvel
2020-09-30 9:27 ` Jonathan Cameron
2020-09-30 17:19 ` Catalin Marinas
2020-06-26 15:58 ` [PATCH v3 2/2] arm64/acpi: disallow writeable AML opregion mapping for EFI code regions Ard Biesheuvel
2021-02-06 3:11 ` Shawn Guo
2021-02-06 8:10 ` Ard Biesheuvel
2021-02-06 10:17 ` Ard Biesheuvel
2021-02-06 10:45 ` Shawn Guo
2020-07-08 16:17 ` [PATCH v3 0/2] arm64/acpi: restrict AML opregion memory access Ard Biesheuvel
2020-07-09 8:42 ` Lorenzo Pieralisi
2020-07-14 19:52 ` Catalin Marinas
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=20200626155832.2323789-1-ardb@kernel.org \
--to=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=sudeep.holla@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).