All of lore.kernel.org
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: linux-arm-kernel@lists.infradead.org,
	Anshuman Khandual <anshuman.khandual@arm.com>,
	Ard Biesheuvel <ardb@kernel.org>
Cc: Will Deacon <will@kernel.org>,
	linux-kernel@vger.kernel.org, Mark Rutland <mark.rutland@arm.com>,
	Steve Capper <steve.capper@arm.com>,
	Mark Brown <broonie@kernel.org>, Marc Zyngier <maz@kernel.org>,
	gshan@redhat.com, Robin Murphy <robin.murphy@arm.com>,
	Steven Price <steven.price@arm.com>
Subject: Re: [PATCH] arm64: mm: account for hotplug memory when randomizing the linear region
Date: Tue, 10 Nov 2020 19:14:18 +0000	[thread overview]
Message-ID: <160503561804.1015659.16599672230432576934.b4-ty@arm.com> (raw)
In-Reply-To: <20201014081857.3288-1-ardb@kernel.org>

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


WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: linux-arm-kernel@lists.infradead.org,
	Anshuman Khandual <anshuman.khandual@arm.com>,
	Ard Biesheuvel <ardb@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
	gshan@redhat.com, Steve Capper <steve.capper@arm.com>,
	Marc Zyngier <maz@kernel.org>,
	linux-kernel@vger.kernel.org, Steven Price <steven.price@arm.com>,
	Mark Brown <broonie@kernel.org>, Will Deacon <will@kernel.org>,
	Robin Murphy <robin.murphy@arm.com>
Subject: Re: [PATCH] arm64: mm: account for hotplug memory when randomizing the linear region
Date: Tue, 10 Nov 2020 19:14:18 +0000	[thread overview]
Message-ID: <160503561804.1015659.16599672230432576934.b4-ty@arm.com> (raw)
In-Reply-To: <20201014081857.3288-1-ardb@kernel.org>

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


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2020-11-10 19:14 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-14  8:18 [PATCH] arm64: mm: account for hotplug memory when randomizing the linear region Ard Biesheuvel
2020-10-15 10:46 ` Will Deacon
2020-10-16 10:26   ` Anshuman Khandual
2020-10-17 12:39 ` Ard Biesheuvel
2020-11-10 19:14 ` Catalin Marinas [this message]
2020-11-10 19:14   ` Catalin Marinas
2020-11-11  3:48   ` Anshuman Khandual
2020-11-11  3:48     ` Anshuman Khandual
2020-11-11  9:11     ` David Hildenbrand
2020-11-11  9:11       ` David Hildenbrand
2020-11-12  9:25     ` Catalin Marinas
2020-11-12  9:25       ` Catalin Marinas
2020-11-13  3:16       ` Anshuman Khandual
2020-11-13  3:16         ` Anshuman Khandual
2020-11-13  6:14         ` Ard Biesheuvel
2020-11-13  6:14           ` Ard Biesheuvel
2020-11-13  7:02           ` Anshuman Khandual
2020-11-13  7:02             ` Anshuman Khandual
2020-11-13  7:06             ` Ard Biesheuvel
2020-11-13  7:06               ` Ard Biesheuvel
2020-11-13  7:40               ` Anshuman Khandual
2020-11-13  7:40                 ` Anshuman Khandual

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=160503561804.1015659.16599672230432576934.b4-ty@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=anshuman.khandual@arm.com \
    --cc=ardb@kernel.org \
    --cc=broonie@kernel.org \
    --cc=gshan@redhat.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=maz@kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=steve.capper@arm.com \
    --cc=steven.price@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.