[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMj1kXGMhmsJmwog6iC+r5Nhyx9QwQkbNdUPSD+UbgZyNvtyzQ@mail.gmail.com>
Date: Wed, 8 Jul 2020 19:17:08 +0300
From: Ard Biesheuvel <ardb@...nel.org>
To: Linux ARM <linux-arm-kernel@...ts.infradead.org>, James Morse <james.morse@....com>
Cc: ACPI Devel Maling List <linux-acpi@...r.kernel.org>, Will Deacon <will@...nel.org>,
Catalin Marinas <catalin.marinas@....com>, Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
Sudeep Holla <sudeep.holla@....com>,
Kernel Hardening <kernel-hardening@...ts.openwall.com>
Subject: Re: [PATCH v3 0/2] arm64/acpi: restrict AML opregion memory access
(+ James)
On Fri, 26 Jun 2020 at 18:58, Ard Biesheuvel <ardb@...nel.org> wrote:
>
> 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
>
With some adult supervision from James (thanks!), I have given this a
spin myself with kexec under QEMU/kvm, to boot a crashkernel, and
everything works as expected.
> arch/arm64/include/asm/acpi.h | 15 +---
> arch/arm64/kernel/acpi.c | 75 ++++++++++++++++++++
> 2 files changed, 76 insertions(+), 14 deletions(-)
>
> --
> 2.27.0
>
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
