mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dave Hansen <dave.hansen@intel.com>
To: Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
	Dave Hansen <dave.hansen@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org, tglx@linutronix.de,
	bp@alien8.de
Subject: Re: [RFC][PATCH] x86/cpu/bugs: Consider having old Intel microcode to be a vulnerability
Date: Tue, 19 Nov 2024 10:49:21 -0800	[thread overview]
Message-ID: <8909243c-3e11-4ce1-a067-710402badbea@intel.com> (raw)
In-Reply-To: <20241119174546.5ehj6yjiqk3baxhh@desk>

On 11/19/24 09:45, Pawan Gupta wrote:
> Sorry for playing the devil's advocate. I am wondering who is the prime
> beneficiary of this change?

At a very high level, it's for folks with new kernels and old microcode.

It's _very_ normal for someone to report a bug and for us upstream folks
to ask them to reproduce on the latest mainline. The moment they do
that, they get the latest microcode list. Folks don't randomly upgrade
to a new kernel for fun in production. But it's hopefully a very normal
activity for folks having problems and launching into debug.

In other words, "new kernel / old microcode" might be relatively rare,
but it still gets used at a *very* critical choke point.

I completely agree with your general sentiment that normal distro users
will get the distro-kernel-provided microcode version list _and_
distro-provided microcode files. This won't help them one bit unless the
distro makes a silly mistake, doesn't do testing, or they somehow
upgrade one package without the other.

  reply	other threads:[~2024-11-19 18:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-07 17:06 Dave Hansen
2024-11-08 23:36 ` Andrew Cooper
2024-11-12 17:15   ` Dave Hansen
2024-11-12  6:37 ` Alex Murray
2024-11-12 15:51   ` Dave Hansen
2024-11-13  3:29     ` Alex Murray
2024-11-13 16:00       ` Dave Hansen
2024-11-13 23:58         ` Alex Murray
2024-11-14  0:37           ` Dave Hansen
2024-11-18  8:35             ` Alex Murray
2024-11-13  9:28     ` Nikolay Borisov
2024-11-14  2:09   ` Andrew Cooper
2024-11-18 20:02     ` Dave Hansen
2024-11-19 17:45 ` Pawan Gupta
2024-11-19 18:49   ` Dave Hansen [this message]
2024-11-19 19:31     ` Pawan Gupta

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=8909243c-3e11-4ce1-a067-710402badbea@intel.com \
    --to=dave.hansen@intel.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®