From: Dave Hansen <dave.hansen@intel.com>
To: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Theodore Ts'o <tytso@mit.edu>,
"Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@linux.intel.com>,
Elena Reshetova <elena.reshetova@intel.com>,
Jun Nakajima <jun.nakajima@intel.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
"Kalra, Ashish" <ashish.kalra@amd.com>,
Sean Christopherson <seanjc@google.com>,
linux-coco@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Randomness on confidential computing platforms
Date: Mon, 29 Jan 2024 08:30:11 -0800 [thread overview]
Message-ID: <276aaeee-cb01-47d3-a3bf-f8fa2e59016c@intel.com> (raw)
In-Reply-To: <20240126134230.1166943-1-kirill.shutemov@linux.intel.com>
On 1/26/24 05:42, Kirill A. Shutemov wrote:
> 3. Panic after enough re-tries of RDRAND/RDSEED instructions fail.
> Another DoS variant against the Guest.
I think Sean was going down the same path, but I really dislike the idea
of having TDX-specific (or CoCo-specific) policy here.
How about we WARN_ON() RDRAND/RDSEED going bonkers? The paranoid folks
can turn on panic_on_warn, if they haven't already.
next prev parent reply other threads:[~2024-01-29 16:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 13:42 [RFC] Randomness on confidential computing platforms Kirill A. Shutemov
2024-01-26 14:46 ` Nikolay Borisov
2024-01-26 15:42 ` Reshetova, Elena
2024-01-26 15:57 ` Daniel P. Berrangé
2024-01-26 16:35 ` Nikolay Borisov
2024-01-29 7:15 ` Reshetova, Elena
2024-01-26 15:23 ` Sean Christopherson
2024-01-29 10:27 ` Kirill A. Shutemov
2024-01-29 16:30 ` Dave Hansen [this message]
2024-01-29 16:37 ` H. Peter Anvin
2024-01-29 16:41 ` Kirill A. Shutemov
2024-01-29 17:07 ` H. Peter Anvin
2024-01-29 18:55 ` Dave Hansen
2024-01-29 20:26 ` Kirill A. Shutemov
2024-01-29 21:04 ` Dave Hansen
2024-01-29 21:17 ` H. Peter Anvin
2024-01-29 21:38 ` H. Peter Anvin
2024-01-29 22:12 ` H. Peter Anvin
2024-01-29 21:33 ` Kirill A. Shutemov
2024-01-29 22:18 ` Dave Hansen
2024-01-29 23:32 ` H. Peter Anvin
2024-01-30 8:19 ` Reshetova, Elena
2024-01-30 8:01 ` Reshetova, Elena
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=276aaeee-cb01-47d3-a3bf-f8fa2e59016c@intel.com \
--to=dave.hansen@intel.com \
--cc=Jason@zx2c4.com \
--cc=ashish.kalra@amd.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=elena.reshetova@intel.com \
--cc=hpa@zytor.com \
--cc=jun.nakajima@intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=tytso@mit.edu \
--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