mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Sneddon <daniel.sneddon@linux.intel.com>
To: Dave Hansen <dave.hansen@intel.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
	<x86@kernel.org>
Cc: pawan.kumar.gupta@linux.intel.com,
	"H. Peter Anvin" <hpa@zytor.com>,
	"open list:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86/bugs: Add missing NO_SSB flag
Date: Wed, 28 Aug 2024 17:01:19 -0700	[thread overview]
Message-ID: <8538c0b5-fde8-4e54-be91-24bcfb31c7ab@linux.intel.com> (raw)
In-Reply-To: <4ff867b7-e5b1-4b91-87cf-127b2e908025@intel.com>

On 8/28/24 16:54, Dave Hansen wrote:
> On 8/28/24 16:50, Daniel Sneddon wrote:
>> On 8/28/24 16:36, Dave Hansen wrote:
>>> On 8/28/24 15:40, Daniel Sneddon wrote:
>>>> The Moorefield and Lightning Mountain Atom processors are
>>>> missing the NO_SSB flag in the vulnerabilities whitelist.
>>>> This will cause unaffected parts to incorrectly be reported
>>>> as vulnerable. Add the missing flag.
>>> It'd be really cool to add two things to these changelogs: First, who
>>> figured this out and how?  Basically, who cares and why?  Second, what
>>> public Intel documentation supports this change?
>> The first thing I can do no problem. The second..... 🙁
> 
> Heh, I went looking just after I asked.  These CPUs are ghosts as far as
> the docs are concerned.  I assume because they are end-of-life'd (or
> whatever the proper name is).  But even saying _that_ in the changelog
> would be helpful.

Will do!

      reply	other threads:[~2024-08-29  0:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-28 22:40 Daniel Sneddon
2024-08-28 23:36 ` Dave Hansen
2024-08-28 23:50   ` Daniel Sneddon
2024-08-28 23:54     ` Dave Hansen
2024-08-29  0:01       ` Daniel Sneddon [this message]

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=8538c0b5-fde8-4e54-be91-24bcfb31c7ab@linux.intel.com \
    --to=daniel.sneddon@linux.intel.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.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

all inboxes | Powered by JetHome®