[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1254edd7-25ee-b73d-da2c-194d38ba7890@infradead.org>
Date: Tue, 8 Dec 2020 09:58:32 -0800
From: Randy Dunlap <rdunlap@...radead.org>
To: Jonathan Corbet <corbet@....net>,
Mathieu Chouquet-Stringer <me@...hieu.digital>
Cc: Borislav Petkov <bp@...en8.de>, Stephen Kitt <steve@....org>,
Andrew Morton <akpm@...ux-foundation.org>,
Kees Cook <keescook@...omium.org>,
"Guilherme G. Piccoli" <gpiccoli@...onical.com>,
Eric Biggers <ebiggers@...gle.com>,
Qais Yousef <qais.yousef@....com>,
Naoki Hayama <naoki.hayama@...eo.co.jp>,
Yue Hu <huyue2@...ong.com>, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Update documentation to reflect what
TAINT_CPU_OUT_OF_SPEC means nowadays
On 12/8/20 9:54 AM, Jonathan Corbet wrote:
> On Wed, 2 Dec 2020 16:32:43 +0100
> Mathieu Chouquet-Stringer <me@...hieu.digital> wrote:
>
>> Hello Jonathan,
>>
>> Here's a patch updating the meaning of TAINT_CPU_OUT_OF_SPEC after
>> Borislav introduced changes in a7e1f67ed29f and upcoming patches in tip.
>>
>> TAINT_CPU_OUT_OF_SPEC now means a bit more what it implies as the
>> flag isn't set just because of a CPU misconfiguration or mismatch.
>> Historically it was for SMP kernel oops on an officially SMP incapable
>> processor but now it also covers CPUs whose MSRs have been incorrectly
>> poked at from userspace, drivers being used on non supported
>> architectures, broken firmware, mismatched CPUs, ...
>>
>> Update documentation and script to reflect that.
>>
>> Signed-off-by: Mathieu Chouquet-Stringer <me@...hieu.digital>
>
> Hearing no objection, I've applied this.
Hm, I was glad to read this new info since my old testing laptop
now tells me that it needs a microcode update. :(
--
~Randy
Powered by blists - more mailing lists