[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <409703ae-6d70-3f6a-d6fc-b7dada3c2797@zytor.com>
Date: Sat, 24 Aug 2019 14:35:40 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: Pavel Machek <pavel@....cz>, linux-kernel@...r.kernel.org
Cc: linux-tip-commits@...r.kernel.org,
"x86@...nel.org" <x86@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>, stable@...r.kernel.org,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
Paolo Bonzini <pbonzini@...hat.com>,
Nathan Chancellor <natechancellor@...il.com>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
Kees Cook <keescook@...omium.org>,
Juergen Gross <jgross@...e.com>,
Josh Poimboeuf <jpoimboe@...hat.com>,
Jonathan Corbet <corbet@....net>,
Ingo Molnar <mingo@...hat.com>, Chen Yu <yu.c.chen@...el.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Andrew Cooper <andrew.cooper3@...rix.com>,
Borislav Petkov <bp@...e.de>,
Tom Lendacky <thomas.lendacky@....com>
Subject: Re: [tip: x86/urgent] x86/CPU/AMD: Clear RDRAND CPUID bit on AMD
family 15h/16h
On 8/24/19 11:19 AM, Pavel Machek wrote:
> 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@....com>
>> AuthorDate: Mon, 19 Aug 2019 15:52:35
>> Committer: Borislav Petkov <bp@...e.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?
>
The kernel should at least be able to set its internal "CPUID" bit, visible
through /proc/cpuinfo.
-hpa
Powered by blists - more mailing lists