From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from theia.8bytes.org (8bytes.org [81.169.241.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 438BF70 for ; Mon, 26 Jul 2021 18:55:34 +0000 (UTC) Received: by theia.8bytes.org (Postfix, from userid 1000) id 99991296; Mon, 26 Jul 2021 20:55:25 +0200 (CEST) Date: Mon, 26 Jul 2021 20:55:24 +0200 From: Joerg Roedel To: Marc Orr Cc: Andi Kleen , Erdem Aktas , Andy Lutomirski , Joerg Roedel , David Rientjes , Borislav Petkov , Sean Christopherson , Andrew Morton , Vlastimil Babka , "Kirill A. Shutemov" , Brijesh Singh , Tom Lendacky , Jon Grimm , Thomas Gleixner , Peter Zijlstra , Paolo Bonzini , Ingo Molnar , "Kaplan, David" , Varad Gautam , Dario Faggioli , x86 , linux-mm@kvack.org, linux-coco@lists.linux.dev Subject: Re: Runtime Memory Validation in Intel-TDX and AMD-SNP Message-ID: References: Precedence: bulk X-Mailing-List: linux-coco@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: On Thu, Jul 22, 2021 at 10:31:27AM -0700, Marc Orr wrote: > IMHO, we need to be completely certain that guest data cannot be > compromised if we're going to remove the requirement that guest memory > only be validated once in a certain state (e.g., from within a crash > kernel). Perhaps it is the case that we're certain that guest data > cannot be compromised from within a crash kernel -- but it's not what > I read in the email exchange. Right, at least SNP has a strict requirement that no memory could be validated or invalidated twice without giving up security guarantees for that memory. Regards, Jörg