From: Jari Ruusu <jariruusu@users.sourceforge.net>
To: noloader@gmail.com
Cc: Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: Re: Loss of performance in RDRAND and RDSEED?
Date: Sun, 03 Jan 2021 11:59:40 +0200 [thread overview]
Message-ID: <5FF1958C.A29E0278@users.sourceforge.net> (raw)
In-Reply-To: CAH8yC8knjfUR2S1NUhWWwBOovvCTWKQ1_MkowVSeRVPKfe-O4w@mail.gmail.com
Jeffrey Walton wrote:
> The hardware is the same, but the OS was upgraded from Fedora 32 to
> Fedora 33. The kernel and possibly intel-microcode have changed
> between May 2020 and January 2021.
>
> I'm aware of this problem with AMD's RDRAND and RDSEED, but it doesn't
> affect Intel machines:
> https://bugzilla.kernel.org/show_bug.cgi?id=85911 (so there should not
> be any remediations in place).
>
> My question is, is anyone aware of what may be responsible for the
> performance loss?
Intel messed up RDRAND security. Microcode fix to avoid data leak includes
getting exclusive lock on some processor internal bus or something like that.
That can be used as DoS tool: run those RDRAND instructions in tight loop,
and all code execution on that CPU does slows down significantly.
https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00320.html
--
Jari Ruusu 4096R/8132F189 12D6 4C3A DCDA 0AA4 27BD ACDF F073 3C80 8132 F189
prev parent reply other threads:[~2021-01-03 10:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-03 3:55 Loss of performance in RDRAND and RDSEED? Jeffrey Walton
2021-01-03 9:59 ` Jari Ruusu [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=5FF1958C.A29E0278@users.sourceforge.net \
--to=jariruusu@users.sourceforge.net \
--cc=linux-crypto@vger.kernel.org \
--cc=noloader@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).