From: Ingo Molnar <mingo@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: linux-tip-commits@vger.kernel.org,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org
Subject: Re: [tip: x86/microcode] x86/cpu: Help users notice when running old Intel microcode
Date: Tue, 22 Apr 2025 08:30:28 +0200 [thread overview]
Message-ID: <aAc3hCVAnNLVo-Xh@gmail.com> (raw)
In-Reply-To: <174526703555.31282.4002502301046834125.tip-bot2@tip-bot2>
* tip-bot2 for Dave Hansen <tip-bot2@linutronix.de> wrote:
> The following commit has been merged into the x86/microcode branch of tip:
>
> Commit-ID: 377781ebaa7c35ab3e91af29074d5f39100372f2
> Gitweb: https://git.kernel.org/tip/377781ebaa7c35ab3e91af29074d5f39100372f2
> Author: Dave Hansen <dave.hansen@linux.intel.com>
> AuthorDate: Mon, 21 Apr 2025 12:56:59 -07:00
> Committer: Dave Hansen <dave.hansen@linux.intel.com>
> CommitterDate: Mon, 21 Apr 2025 12:59:29 -07:00
>
> x86/cpu: Help users notice when running old Intel microcode
>
> Changes from v4:
> - Update list from commit: 8ac9378 microcode-20241112 Release
>
> Changes from v3:
> - Update changelog and documentation to clarify behavior when
> microcode is updated at runtime.
>
> Changes from v2:
> - Make cpu_latest_microcode[] static
> - Add a pr_info() when the CPU is not in the microcode version list
>
> Changes from v1:
> - Flesh out changelog
> - Add Documentation/
> - add_taint() and pr_warn() in addition to vulnerabilities/ file
> - Add checks for running under VMMs. Do not taint and
> report vulnerability as unknown.
These should not be part of a commit log.
> From: Dave Hansen <dave.hansen@linux.intel.com>
> + /* Give new microocode a pass: */
> + if (boot_cpu_data.microcode >= m->driver_data)
> + return false;
Typo:
s/microocode
/microcode
I've amended the commit in tip:x86/microcode accordingly, please let me
know if this version is fine to you too:
9127865b15eb ("x86/cpu: Help users notice when running old Intel microcode")
Thanks,
Ingo
next prev parent reply other threads:[~2025-04-22 6:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-21 20:23 [tip: x86/microcode] x86/cpu: Help users notice when running old Intel microcode tip-bot2 for Dave Hansen
2025-04-22 6:30 ` Ingo Molnar [this message]
2025-04-22 6:36 ` Ingo Molnar
2025-04-22 14:05 ` Dave Hansen
-- strict thread matches above, loose matches on Subject: below --
2025-04-22 6:36 tip-bot2 for Dave Hansen
2025-04-22 6:47 tip-bot2 for Dave Hansen
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=aAc3hCVAnNLVo-Xh@gmail.com \
--to=mingo@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--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.