All of lore.kernel.org
 help / color / mirror / Atom feed
From: Breno Leitao <leitao@debian.org>
To: Dave Hansen <dave.hansen@intel.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Josh Poimboeuf <jpoimboe@kernel.org>,
	Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
	leit@meta.com,
	"open list:X86 ARCHITECTURE (32-BIT AND 64-BIT)" 
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] x86/bugs: Add a separate config for each mitigation
Date: Thu, 28 Sep 2023 06:57:54 -0700	[thread overview]
Message-ID: <ZRWGYn4Y+2v/S6Ar@gmail.com> (raw)
In-Reply-To: <a5fbcf09-2445-28f1-4113-0de4f72b7f90@intel.com>

On Thu, Sep 28, 2023 at 06:40:18AM -0700, Dave Hansen wrote:
> On 9/28/23 05:45, Breno Leitao wrote:
> > 1) Create one Kconfig entry per mitigation, so, the user can pick and
> > choose what to enable and disable. (Version 3 of this patch. May need a
> > re-spin due to the new mitigations being added.)
> 
> This means, what, roughly 18 today?
> 
> #define X86_BUG_CPU_MELTDOWN		X86_BUG(14)
> ...
> #define X86_BUG_GDS                     X86_BUG(30)
> 
> Plus two bonus ones:
> 
> #define X86_BUG_SRSO                    X86_BUG(1*32 + 0)
> #define X86_BUG_DIV0                    X86_BUG(1*32 + 1)
> 
> ... and we've slowed down the rate at which we're adding these, but
> we're still seeing a couple a year.
> 
> Perhaps Pawan and the others actually _doing_ the patches for these can
> speak up, but I don't think adding a Kconfig option will be too much
> additional work for each new X86_BUG.
> 
> I still think it's highly unlikely that someone will come through and
> pick and choose among a few dozen vulnerabilities.

That is what my experience tells me as well. You either have a insecure
and fast kernel, or a hardened one. In some big companies, you can have
both, and choose which one you want to boot depending on the workload.

  reply	other threads:[~2023-09-28 13:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-28 14:21 [PATCH v3] x86/bugs: Add a separate config for each mitigation leitao
2023-09-28 12:45 ` Breno Leitao
2023-09-28 13:40   ` Dave Hansen
2023-09-28 13:57     ` Breno Leitao [this message]
2023-09-28 16:33     ` Pawan Gupta
2023-10-05 16:25   ` Borislav Petkov
2023-10-05 18:29     ` Linus Torvalds
2023-10-06  9:54       ` Borislav Petkov
2023-10-06 10:59         ` 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=ZRWGYn4Y+2v/S6Ar@gmail.com \
    --to=leitao@debian.org \
    --cc=bp@alien8.de \
    --cc=dave.hansen@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=jpoimboe@kernel.org \
    --cc=leit@meta.com \
    --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.