linux-kernel - Re: [PATCH 4/5] arm64: Verify CPU errata work arounds on hotplugged CPU

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <570FD817.5050704@arm.com>
Date:	Thu, 14 Apr 2016 18:49:11 +0100
From:	Suzuki K Poulose <Suzuki.Poulose@....com>
To:	Will Deacon <will.deacon@....com>
Cc:	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	marc.zyngier@....com, catalin.marinas@....com,
	mark.rutland@....com, Vadim.Lomovtsev@...iumnetworks.com,
	Andre Przywara <andre.przywara@....com>
Subject: Re: [PATCH 4/5] arm64: Verify CPU errata work arounds on hotplugged
 CPU

On 14/04/16 18:39, Will Deacon wrote:
> On Wed, Apr 06, 2016 at 12:24:13PM +0100, Suzuki K Poulose wrote:
>> CPU Errata work arounds are detected and applied to the
>> kernel code at boot time and the data is then freed up.
>> If a new hotplugged CPU requires a work around which
>> was not applied at boot time, there is nothing we can
>> do but simply fail the booting.
>
> Hmm, wouldn't it be better not to free the alternative text for errata
> workarounds instead?

We could. I don't have a strong opinion. If there are no objections, I could
adopt it.

Cheers
Suzuki