All of lore.kernel.org
 help / color / mirror / Atom feed
From: Breno Leitao <leitao@debian.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Daniel Sneddon <daniel.sneddon@linux.intel.com>,
	Josh Poimboeuf <jpoimboe@kernel.org>,
	mingo@redhat.com, Thomas Gleixner <tglx@linutronix.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 01/10] x86/bugs: Add a separate config for GDS
Date: Mon, 15 Jul 2024 05:14:54 -0700	[thread overview]
Message-ID: <ZpUSvl5eKgkLeJrg@gmail.com> (raw)
In-Reply-To: <20240712172132.GFZpFmHBJHte2xS1fr@fat_crate.local>

Hello Borislav,

On Fri, Jul 12, 2024 at 07:21:32PM +0200, Borislav Petkov wrote:
> On Mon, Apr 22, 2024 at 09:58:15AM -0700, Breno Leitao wrote:
> > +config MITIGATION_GDS
> > +	bool "Mitigate Gather Data Sampling"
> > +	depends on CPU_SUP_INTEL
> > +	default y
> > +	help
> > +	  Enable mitigation for Gather Data Sampling (GDS). GDS is a hardware
> > +	  vulnerability which allows unprivileged speculative access to data
> > +	  which was previously stored in vector registers. The attacker uses gather
> > +	  instructions to infer the stale vector register data.
> > +
> >  config MITIGATION_GDS_FORCE
> 
> Btw, can we get rid of that thing, while at it?

Sure, I will send a v4 and get rid of GDS_FORCE_MITIGATION completely.

Thanks for the review.

--breno

  reply	other threads:[~2024-07-15 12:14 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-22 16:58 [PATCH v3 00/10] x86/bugs: Separate config for mitigations Breno Leitao
2024-04-22 16:58 ` [PATCH v3 01/10] x86/bugs: Add a separate config for GDS Breno Leitao
2024-07-12 17:21   ` Borislav Petkov
2024-07-15 12:14     ` Breno Leitao [this message]
2024-07-15 12:17       ` Borislav Petkov
2024-07-15 13:35         ` Breno Leitao
2024-07-15 13:43           ` Borislav Petkov
2024-07-15 14:20             ` Breno Leitao
2024-07-16 18:51         ` Daniel Sneddon
2024-07-16 19:10           ` Borislav Petkov
2024-04-22 16:58 ` [PATCH v3 02/10] x86/bugs: Add a separate config for MDS Breno Leitao
2024-04-22 16:58 ` [PATCH v3 03/10] x86/bugs: Add a separate config for TAA Breno Leitao
2024-04-22 16:58 ` [PATCH v3 04/10] x86/bugs: Add a separate config for MMIO Stable Data Breno Leitao
2024-04-22 16:58 ` [PATCH v3 05/10] x86/bugs: Add a separate config for L1TF Breno Leitao
2024-04-22 16:58 ` [PATCH v3 06/10] x86/bugs: Add a separate config for RETBLEED Breno Leitao
2024-04-22 16:58 ` [PATCH v3 07/10] x86/bugs: Add a separate config for Spectre v1 Breno Leitao
2024-04-22 16:58 ` [PATCH v3 08/10] x86/bugs: Add a separate config for SRBDS Breno Leitao
2024-04-22 16:58 ` [PATCH v3 09/10] x86/bugs: Add a separate config for Spectre V2 Breno Leitao
2024-04-22 16:58 ` [PATCH v3 10/10] x86/bugs: Add a separate config for SSB Breno Leitao
2024-07-29  9:21 ` [PATCH v3 00/10] x86/bugs: Separate config for mitigations Borislav Petkov
2024-07-29 16:27   ` Breno Leitao

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=ZpUSvl5eKgkLeJrg@gmail.com \
    --to=leitao@debian.org \
    --cc=bp@alien8.de \
    --cc=daniel.sneddon@linux.intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=jpoimboe@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=pawan.kumar.gupta@linux.intel.com \
    --cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.