Re: [tip: x86/urgent] x86/CPU/AMD: Clear RDRAND CPUID bit on AMD family 15h/16h
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [tip: x86/urgent] x86/CPU/AMD: Clear RDRAND CPUID bit on AMD family 15h/16h
- From: Pavel Machek <pavel@xxxxxx>
- Date: Sat, 24 Aug 2019 20:19:29 +0200
- Cc: linux-tip-commits@xxxxxxxxxxxxxxx, "x86@xxxxxxxxxx" <x86@xxxxxxxxxx>, Thomas Gleixner <tglx@xxxxxxxxxxxxx>, stable@xxxxxxxxxxxxxxx, "Rafael J. Wysocki" <rjw@xxxxxxxxxxxxx>, Paolo Bonzini <pbonzini@xxxxxxxxxx>, Nathan Chancellor <natechancellor@xxxxxxxxx>, "linux-pm@xxxxxxxxxxxxxxx" <linux-pm@xxxxxxxxxxxxxxx>, "linux-doc@xxxxxxxxxxxxxxx" <linux-doc@xxxxxxxxxxxxxxx>, Kees Cook <keescook@xxxxxxxxxxxx>, Juergen Gross <jgross@xxxxxxxx>, Josh Poimboeuf <jpoimboe@xxxxxxxxxx>, Jonathan Corbet <corbet@xxxxxxx>, Ingo Molnar <mingo@xxxxxxxxxx>, "H. Peter Anvin" <hpa@xxxxxxxxx>, Chen Yu <yu.c.chen@xxxxxxxxx>, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Borislav Petkov <bp@xxxxxxx>, Tom Lendacky <thomas.lendacky@xxxxxxx>
- In-reply-to: <156652264945.9541.4969272027980914591.tip-bot2@tip-bot2>
- References: <7543af91666f491547bd86cebb1e17c66824ab9f.1566229943.git.thomas.lendacky@amd.com> <156652264945.9541.4969272027980914591.tip-bot2@tip-bot2>
- User-agent: Mutt/1.5.23 (2014-03-12)
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@xxxxxxx>
> AuthorDate: Mon, 19 Aug 2019 15:52:35
> Committer: Borislav Petkov <bp@xxxxxxx>
> 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:
signature.asc
Description: Digital signature
[Index of Archives]
[Linux Stable Commits]
[Linux Stable Kernel]
[Linux Kernel]
[Linux USB Devel]
[Linux Video &Media]
[Linux Audio Users]
[Yosemite News]
[Linux SCSI]