From: Breno Leitao <leitao@debian.org>
To: Borislav Petkov <bp@alien8.de>
Cc: pawan.kumar.gupta@linux.intel.com,
Thomas Gleixner <tglx@linutronix.de>,
paul@paul-moore.com, leit@meta.com, x86@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpu/bugs: Disable CPU mitigations at compilation time
Date: Tue, 13 Jun 2023 09:02:50 -0700 [thread overview]
Message-ID: <ZIiTKttkucqiE8wJ@gmail.com> (raw)
In-Reply-To: <20230612170532.GOZIdQXLYZCGKZQFXv@fat_crate.local>
On Mon, Jun 12, 2023 at 07:05:32PM +0200, Borislav Petkov wrote:
> On Mon, Jun 12, 2023 at 09:37:07AM -0700, Breno Leitao wrote:
> > I am not sure if these bugs (MDS, TAA) are speculations related. Pawan
> > could help us here.
>
> "Microarchitectural Data Sampling is a hardware vulnerability which allows
> unprivileged speculative access..."
>
> "TAA is a hardware vulnerability that allows unprivileged speculative
> access to data which is available in various CPU..."
Is it OK if I send a patch that would disable these mitigations if
CONFIG_SPECULATION_MITIGATIONS is set to "no"?
Thank you!
next prev parent reply other threads:[~2023-06-13 16:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 12:06 [PATCH] cpu/bugs: Disable CPU mitigations at compilation time Breno Leitao
2023-06-09 17:33 ` Borislav Petkov
2023-06-12 11:22 ` David Laight
2023-06-12 11:51 ` Borislav Petkov
2023-06-12 12:16 ` David Laight
2023-06-12 13:27 ` Borislav Petkov
2023-06-10 22:37 ` Thomas Gleixner
2023-06-12 12:54 ` Breno Leitao
2023-06-12 13:32 ` Borislav Petkov
2023-06-12 13:46 ` Breno Leitao
2023-06-12 13:53 ` Borislav Petkov
2023-06-12 14:16 ` Breno Leitao
2023-06-12 16:08 ` Borislav Petkov
2023-06-12 16:37 ` Breno Leitao
2023-06-12 17:05 ` Borislav Petkov
2023-06-13 16:02 ` Breno Leitao [this message]
2023-06-13 16:20 ` Borislav Petkov
2023-06-12 17:26 ` Thomas Gleixner
2023-06-12 18:06 ` Randy Dunlap
2023-06-12 18:13 ` Borislav Petkov
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=ZIiTKttkucqiE8wJ@gmail.com \
--to=leitao@debian.org \
--cc=bp@alien8.de \
--cc=leit@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=pawan.kumar.gupta@linux.intel.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).