[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <159475635407.4337.14038873676675267041.b4-ty@arm.com>
Date: Tue, 14 Jul 2020 20:52:41 +0100
From: Catalin Marinas <catalin.marinas@....com>
To: Ard Biesheuvel <ardb@...nel.org>,
linux-arm-kernel@...ts.infradead.org
Cc: Will Deacon <will@...nel.org>,
sudeep.holla@....com,
kernel-hardening@...ts.openwall.com,
linux-acpi@...r.kernel.org,
lorenzo.pieralisi@....com
Subject: Re: [PATCH v3 0/2] arm64/acpi: restrict AML opregion memory access
On Fri, 26 Jun 2020 17:58:30 +0200, Ard Biesheuvel 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)
>
> [...]
Applied to arm64 (for-next/acpi), thanks!
[1/2] arm64/acpi: disallow AML memory opregions to access kernel memory
https://git.kernel.org/arm64/c/1583052d111f
[2/2] arm64/acpi: disallow writeable AML opregion mapping for EFI code regions
https://git.kernel.org/arm64/c/325f5585ec36
--
Catalin
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.
