[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <160503561804.1015659.16599672230432576934.b4-ty@arm.com>
Date: Tue, 10 Nov 2020 19:14:18 +0000
From: Catalin Marinas <catalin.marinas@....com>
To: linux-arm-kernel@...ts.infradead.org,
Anshuman Khandual <anshuman.khandual@....com>,
Ard Biesheuvel <ardb@...nel.org>
Cc: Will Deacon <will@...nel.org>, linux-kernel@...r.kernel.org,
Mark Rutland <mark.rutland@....com>,
Steve Capper <steve.capper@....com>,
Mark Brown <broonie@...nel.org>, Marc Zyngier <maz@...nel.org>,
gshan@...hat.com, Robin Murphy <robin.murphy@....com>,
Steven Price <steven.price@....com>
Subject: Re: [PATCH] arm64: mm: account for hotplug memory when randomizing the linear region
On Wed, 14 Oct 2020 10:18:57 +0200, Ard Biesheuvel wrote:
> As a hardening measure, we currently randomize the placement of
> physical memory inside the linear region when KASLR is in effect.
> Since the random offset at which to place the available physical
> memory inside the linear region is chosen early at boot, it is
> based on the memblock description of memory, which does not cover
> hotplug memory. The consequence of this is that the randomization
> offset may be chosen such that any hotplugged memory located above
> memblock_end_of_DRAM() that appears later is pushed off the end of
> the linear region, where it cannot be accessed.
>
> [...]
Applied to arm64 (for-next/mem-hotplug), thanks!
[1/1] arm64: mm: account for hotplug memory when randomizing the linear region
https://git.kernel.org/arm64/c/97d6786e0669
--
Catalin
Powered by blists - more mailing lists