linux-kernel - Re: [PATCH] arm64: consistently use reserved_pg

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <160503567612.1015740.6410821724474192857.b4-ty@arm.com>
Date:   Tue, 10 Nov 2020 19:17:56 +0000
From:   Catalin Marinas <catalin.marinas@....com>
To:     Anshuman Khandual <anshuman.khandual@....com>,
        linux-arm-kernel@...ts.infradead.org,
        Mark Rutland <mark.rutland@....com>
Cc:     Will Deacon <will@...nel.org>, Marc Zyngier <maz@...nel.org>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] arm64: consistently use reserved_pg_dir

On Tue, 3 Nov 2020 10:22:29 +0000, Mark Rutland wrote:
> Depending on configuration options and specific code paths, we either
> use the empty_zero_page or the configuration-dependent reserved_ttbr0
> as a reserved value for TTBR{0,1}_EL1.
> 
> To simplify this code, let's always allocate and use the same
> reserved_pg_dir, replacing reserved_ttbr0. Note that this is allocated
> (and hence pre-zeroed), and is also marked as read-only in the kernel
> Image mapping.
> 
> [...]

Applied to arm64 (for-next/misc), thanks!

[1/1] arm64: consistently use reserved_pg_dir
      https://git.kernel.org/arm64/c/833be850f1ca

-- 
Catalin