From: Pavel Machek <pavel@ucw.cz>
To: linux-kernel@vger.kernel.org
Cc: linux-tip-commits@vger.kernel.org,
"x86@kernel.org" <x86@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
stable@vger.kernel.org, "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Paolo Bonzini <pbonzini@redhat.com>,
Nathan Chancellor <natechancellor@gmail.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
Kees Cook <keescook@chromium.org>,
Juergen Gross <jgross@suse.com>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Jonathan Corbet <corbet@lwn.net>, Ingo Molnar <mingo@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>, Chen Yu <yu.c.chen@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Borislav Petkov <bp@suse.de>,
Tom Lendacky <thomas.lendacky@amd.com>
Subject: Re: [tip: x86/urgent] x86/CPU/AMD: Clear RDRAND CPUID bit on AMD family 15h/16h
Date: Sat, 24 Aug 2019 20:19:29 +0200 [thread overview]
Message-ID: <20190824181929.GA18551@amd> (raw)
In-Reply-To: <156652264945.9541.4969272027980914591.tip-bot2@tip-bot2>
[-- Attachment #1: Type: text/plain, Size: 1184 bytes --]
On Fri 2019-08-23 01:10:49, tip-bot2 for Tom Lendacky wrote:
> The following commit has been merged into the x86/urgent branch of tip:
>
> Commit-ID: c49a0a80137c7ca7d6ced4c812c9e07a949f6f24
> Gitweb: https://git.kernel.org/tip/c49a0a80137c7ca7d6ced4c812c9e07a949f6f24
> Author: Tom Lendacky <thomas.lendacky@amd.com>
> AuthorDate: Mon, 19 Aug 2019 15:52:35
> Committer: Borislav Petkov <bp@suse.de>
> CommitterDate: Mon, 19 Aug 2019 19:42:52 +02:00
>
> x86/CPU/AMD: Clear RDRAND CPUID bit on AMD family 15h/16h
>
> There have been reports of RDRAND issues after resuming from suspend on
> some AMD family 15h and family 16h systems. This issue stems from a BIOS
> not performing the proper steps during resume to ensure RDRAND continues
> to function properly.
There are quite a few unanswered questions here.
a) Is there/should there be CVE for this?
b) Can we perform proper steps in kernel, thus making RDRAND usable
even when BIOS is buggy?
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2019-08-24 18:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 15:52 [PATCH v2] x86/CPU/AMD: Clear RDRAND CPUID bit on AMD family 15h/16h Lendacky, Thomas
2019-08-23 1:10 ` [tip: x86/urgent] " tip-bot2 for Tom Lendacky
2019-08-24 13:50 ` Sasha Levin
2019-08-24 19:13 ` Borislav Petkov
2019-08-24 18:19 ` Pavel Machek [this message]
2019-08-24 21:35 ` H. Peter Anvin
2019-10-08 21:20 ` 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=20190824181929.GA18551@amd \
--to=pavel@ucw.cz \
--cc=akpm@linux-foundation.org \
--cc=andrew.cooper3@citrix.com \
--cc=bp@suse.de \
--cc=corbet@lwn.net \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=jpoimboe@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=natechancellor@gmail.com \
--cc=pbonzini@redhat.com \
--cc=rjw@rjwysocki.net \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=x86@kernel.org \
--cc=yu.c.chen@intel.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 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.