From: Borislav Petkov <bp@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Pu Wen <puwen@hygon.cn>, Thomas Gleixner <tglx@linutronix.de>,
Tom Lendacky <thomas.lendacky@amd.com>,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
the arch/x86 maintainers <x86@kernel.org>
Subject: Re: [GIT pull] x86/urgent for 5.3-rc5
Date: Tue, 27 Aug 2019 19:59:54 +0200 [thread overview]
Message-ID: <20190827175954.GI27871@zn.tnic> (raw)
In-Reply-To: <CAHk-=wj+w5+dicacZhtUG94r4ee5zEMM4FngC8dq1bB2X+V5Xg@mail.gmail.com>
On Tue, Aug 27, 2019 at 10:46:42AM -0700, Linus Torvalds wrote:
> No hurry, and I don't care deeply when this goes in. It looks safe and
> harmless, so any time as far as I'm concerned - whatever is most
> convenient for people.
>
> This is more of a "let's protect against any future issues" than
> anything critical right now.
Yeah.
> And I suspect it just means that next time somebody screws up rdrand,
> they'll screw it up to be a simple counter instead of just returning
> all-ones,
I'm reading this, and, for some reason, not even the slightest ounce of
surprise is materializing in me. I wonder why that is...
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer, HRB 247165, AG München
next prev parent reply other threads:[~2019-08-27 18:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-25 9:43 [GIT pull] irq/urgent for 5.3-rc5 Thomas Gleixner
2019-08-25 9:43 ` [GIT pull] x86/urgent " Thomas Gleixner
2019-08-25 17:18 ` Linus Torvalds
2019-08-25 17:30 ` Borislav Petkov
2019-08-25 17:37 ` Linus Torvalds
2019-08-25 18:29 ` Borislav Petkov
2019-08-25 18:38 ` Linus Torvalds
2019-08-25 19:32 ` Borislav Petkov
2019-08-25 19:35 ` Linus Torvalds
2019-08-25 19:49 ` Borislav Petkov
2019-08-25 19:59 ` Linus Torvalds
2019-08-25 20:17 ` Borislav Petkov
2019-08-26 12:53 ` Borislav Petkov
2019-08-27 16:55 ` Linus Torvalds
2019-08-27 17:39 ` Borislav Petkov
2019-08-27 17:46 ` Linus Torvalds
2019-08-27 17:59 ` Borislav Petkov [this message]
2019-08-28 15:20 ` David Sterba
2019-08-28 15:53 ` David Sterba
2019-10-02 19:09 ` [tip: x86/cpu] x86/rdrand: Sanity-check RDRAND output tip-bot2 for Borislav Petkov
2019-08-25 17:40 ` [GIT pull] x86/urgent for 5.3-rc5 pr-tracker-bot
2019-08-25 9:43 ` [GIT pull] sched/urgent " Thomas Gleixner
2019-08-25 17:40 ` pr-tracker-bot
2019-08-25 9:43 ` [GIT pull] timers/urgent " Thomas Gleixner
2019-08-25 17:40 ` pr-tracker-bot
2019-08-25 9:43 ` [GIT pull] perf/urgent " Thomas Gleixner
2019-08-25 17:40 ` pr-tracker-bot
2019-08-25 17:40 ` [GIT pull] irq/urgent " pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2019-08-18 11:34 [GIT pull] efi/urgent " Thomas Gleixner
2019-08-18 11:34 ` [GIT pull] x86/urgent " Thomas Gleixner
2019-08-18 16:55 ` pr-tracker-bot
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=20190827175954.GI27871@zn.tnic \
--to=bp@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=puwen@hygon.cn \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=torvalds@linux-foundation.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