public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: linux-kernel@vger.kernel.org
Cc: linux-tip-commits@vger.kernel.org, stable@vger.kernel.org,
	Gregory Price <gourry@gourry.net>,
	"Borislav Petkov (AMD)" <bp@alien8.de>,
	x86@kernel.org
Subject: Re: [tip: x86/urgent] x86/CPU/AMD: Add RDSEED fix for Zen5
Date: Thu, 30 Oct 2025 19:05:16 +0100	[thread overview]
Message-ID: <aQOo3LcsdU23q1i2@zx2c4.com> (raw)
In-Reply-To: <176165291198.2601451.3074910014537130674.tip-bot2@tip-bot2>

Hi,

On Tue, Oct 28, 2025 at 12:01:51PM -0000, tip-bot2 for Gregory Price wrote:
> x86/CPU/AMD: Add RDSEED fix for Zen5
> 
> There's an issue with RDSEED's 16-bit and 32-bit register output
> variants on Zen5 which return a random value of 0 "at a rate inconsistent
> with randomness while incorrectly signaling success (CF=1)". Search the
> web for AMD-SB-7055 for more detail.
> 
> Add a fix glue which checks microcode revisions.
> 
>   [ bp: Add microcode revisions checking, rewrite. ]
> 
> Cc: stable@vger.kernel.org
> Signed-off-by: Gregory Price <gourry@gourry.net>
> Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
> Link: https://lore.kernel.org/r/20251018024010.4112396-1-gourry@gourry.net

I didn't see this on LKML or any mailing list before this appeared in
tip. Did I miss something?

Jason

  reply	other threads:[~2025-10-30 18:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-28 12:01 [tip: x86/urgent] x86/CPU/AMD: Add RDSEED fix for Zen5 tip-bot2 for Gregory Price
2025-10-30 18:05 ` Jason A. Donenfeld [this message]
2025-10-30 21:48   ` Jason A. Donenfeld
2025-11-03 13:59 ` Peter Jung
2025-11-03 14:28   ` Borislav Petkov
2025-11-03 16:12   ` Thomas Gleixner
2025-11-24 22:18   ` Pavel Machek

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=aQOo3LcsdU23q1i2@zx2c4.com \
    --to=jason@zx2c4.com \
    --cc=bp@alien8.de \
    --cc=gourry@gourry.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox