From: Jonathan Corbet <corbet@lwn.net>
To: Mathieu Chouquet-Stringer <me@mathieu.digital>
Cc: Borislav Petkov <bp@alien8.de>, Stephen Kitt <steve@sk2.org>,
Andrew Morton <akpm@linux-foundation.org>,
Kees Cook <keescook@chromium.org>,
"Guilherme G. Piccoli" <gpiccoli@canonical.com>,
Eric Biggers <ebiggers@google.com>,
Randy Dunlap <rdunlap@infradead.org>,
Qais Yousef <qais.yousef@arm.com>,
Naoki Hayama <naoki.hayama@lineo.co.jp>,
Yue Hu <huyue2@yulong.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Update documentation to reflect what TAINT_CPU_OUT_OF_SPEC means nowadays
Date: Tue, 8 Dec 2020 10:54:39 -0700 [thread overview]
Message-ID: <20201208105439.23e2349b@lwn.net> (raw)
In-Reply-To: <20201202153244.709752-1-me@mathieu.digital>
On Wed, 2 Dec 2020 16:32:43 +0100
Mathieu Chouquet-Stringer <me@mathieu.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@mathieu.digital>
Hearing no objection, I've applied this.
Thanks,
jon
next prev parent reply other threads:[~2020-12-08 17:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 15:32 [PATCH] Update documentation to reflect what TAINT_CPU_OUT_OF_SPEC means nowadays Mathieu Chouquet-Stringer
2020-12-08 17:54 ` Jonathan Corbet [this message]
2020-12-08 17:58 ` Randy Dunlap
2020-12-08 23:11 ` Mathieu Chouquet-Stringer
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=20201208105439.23e2349b@lwn.net \
--to=corbet@lwn.net \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=ebiggers@google.com \
--cc=gpiccoli@canonical.com \
--cc=huyue2@yulong.com \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=me@mathieu.digital \
--cc=naoki.hayama@lineo.co.jp \
--cc=qais.yousef@arm.com \
--cc=rdunlap@infradead.org \
--cc=steve@sk2.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox