From: David Laight <David.Laight@ACULAB.COM>
To: 'Borislav Petkov' <bp@alien8.de>, KP Singh <kpsingh@kernel.org>
Cc: "Pawan Gupta" <pawan.kumar.gupta@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"pjt@google.com" <pjt@google.com>,
"evn@google.com" <evn@google.com>,
"jpoimboe@kernel.org" <jpoimboe@kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"x86@kernel.org" <x86@kernel.org>,
"hpa@zytor.com" <hpa@zytor.com>,
"peterz@infradead.org" <peterz@infradead.org>,
"kim.phillips@amd.com" <kim.phillips@amd.com>,
"alexandre.chartre@oracle.com" <alexandre.chartre@oracle.com>,
"daniel.sneddon@linux.intel.com" <daniel.sneddon@linux.intel.com>,
"corbet@lwn.net" <corbet@lwn.net>, "bp@suse.de" <bp@suse.de>,
"linyujun809@huawei.com" <linyujun809@huawei.com>,
"jmattson@google.com" <jmattson@google.com>,
"José Oliveira" <joseloliveira11@gmail.com>,
"Rodrigo Branco" <rodrigo@kernelhacking.com>,
"Alexandra Sandulescu" <aesa@google.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: RE: [PATCH v2 1/2] x86/speculation: Allow enabling STIBP with legacy IBRS
Date: Wed, 22 Feb 2023 13:56:40 +0000 [thread overview]
Message-ID: <2cfb89db3cfb418cb3e929b1c0d80ee5@AcuMS.aculab.com> (raw)
In-Reply-To: <Y/YLYbr5CV2Vtxph@zn.tnic>
From: Borislav Petkov
> Sent: 22 February 2023 12:33
>
> On Tue, Feb 21, 2023 at 09:49:57PM -0800, KP Singh wrote:
> > That is a bit more complicated as, for now, the user is not really
> > exposed to STIBP explicitly yet.
>
> Remember that we're exposing the normal user to a gazillion switches
> already. And not every user has done a PhD in hw vulns like we were
> forced to in the last, at least 5, years.
It is also worth explaining the acronyms and what the mitigations
actually do.
There are also the big family where disabling hyperthreading
is probably a better way to avoid the vulnerability.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2023-02-22 13:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 18:49 [PATCH v2 1/2] x86/speculation: Allow enabling STIBP with legacy IBRS KP Singh
2023-02-21 18:49 ` [PATCH v2 2/2] Documentation/hw-vuln: Document the interaction between IBRS and STIBP KP Singh
2023-02-23 14:52 ` Borislav Petkov
2023-02-24 3:30 ` KP Singh
2023-02-26 1:42 ` KP Singh
2023-02-21 19:29 ` [PATCH v2 1/2] x86/speculation: Allow enabling STIBP with legacy IBRS Greg KH
2023-02-21 19:29 ` Greg KH
2023-02-21 19:35 ` KP Singh
2023-02-21 19:47 ` Greg KH
2023-02-21 19:57 ` Borislav Petkov
2023-02-21 20:09 ` Greg KH
2023-02-21 20:23 ` Borislav Petkov
2023-02-22 3:07 ` Pawan Gupta
2023-02-22 5:49 ` KP Singh
2023-02-22 8:25 ` Pawan Gupta
2023-02-22 12:32 ` Borislav Petkov
2023-02-22 13:56 ` David Laight [this message]
2023-02-22 12:24 ` Borislav Petkov
2023-02-22 17:16 ` KP Singh
2023-02-22 17:48 ` Borislav Petkov
2023-02-22 19:41 ` KP Singh
2023-02-23 12:44 ` Borislav Petkov
2023-02-26 1:50 ` KP Singh
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=2cfb89db3cfb418cb3e929b1c0d80ee5@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=aesa@google.com \
--cc=alexandre.chartre@oracle.com \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=corbet@lwn.net \
--cc=daniel.sneddon@linux.intel.com \
--cc=evn@google.com \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joseloliveira11@gmail.com \
--cc=jpoimboe@kernel.org \
--cc=kim.phillips@amd.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linyujun809@huawei.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=rodrigo@kernelhacking.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox