From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from lists.xenproject.org (lists.xenproject.org [192.237.175.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 304DDC25B77 for ; Thu, 16 May 2024 05:22:09 +0000 (UTC) Received: from list by lists.xenproject.org with outflank-mailman.722801.1127111 (Exim 4.92) (envelope-from ) id 1s7TYm-0002lH-Qs; Thu, 16 May 2024 05:21:44 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 722801.1127111; Thu, 16 May 2024 05:21:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1s7TYm-0002lA-Nz; Thu, 16 May 2024 05:21:44 +0000 Received: by outflank-mailman (input) for mailman id 722801; Thu, 16 May 2024 05:21:43 +0000 Received: from se1-gles-flk1-in.inumbo.com ([94.247.172.50] helo=se1-gles-flk1.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1s7TYl-0002l4-KM for xen-devel@lists.xenproject.org; Thu, 16 May 2024 05:21:43 +0000 Received: from mailhost.m5p.com (mailhost.m5p.com [74.104.188.4]) by se1-gles-flk1.inumbo.com (Halon) with ESMTPS id 2bd96466-1344-11ef-b4bb-af5377834399; Thu, 16 May 2024 07:21:40 +0200 (CEST) Received: from m5p.com (mailhost.m5p.com [IPv6:2001:470:1f07:15ff:0:0:0:f7]) by mailhost.m5p.com (8.17.1/8.17.1) with ESMTPS id 44G5LMOX042847 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Thu, 16 May 2024 01:21:28 -0400 (EDT) (envelope-from ehem@m5p.com) Received: (from ehem@localhost) by m5p.com (8.17.1/8.15.2/Submit) id 44G5LL92042846; Wed, 15 May 2024 22:21:21 -0700 (PDT) (envelope-from ehem) X-BeenThere: xen-devel@lists.xenproject.org List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xenproject.org Precedence: list Sender: "Xen-devel" X-Inumbo-ID: 2bd96466-1344-11ef-b4bb-af5377834399 Date: Wed, 15 May 2024 22:21:21 -0700 From: Elliott Mitchell To: Kelly Choi Cc: Jan Beulich , xen-devel@lists.xenproject.org, Andrew Cooper , Wei Liu , Roger Pau =?iso-8859-1?Q?Monn=E9?= Subject: Re: Serious AMD-Vi(?) issue Message-ID: References: <2aa4d1f4-ff37-4f12-bfbb-3ef5ad3f6fdd@suse.com> <08503965-4ba9-4fe3-a176-895623f4ad92@suse.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On Wed, May 15, 2024 at 02:40:31PM +0100, Kelly Choi wrote: > > As explained previously, we are happy to help resolve issues and provide > advice where necessary. However, to do this, our developers need the > relevant information to provide accurate resolutions. Given that our > developers have repeatedly voiced their concerns, and are debugging this > out of interest, please help us by providing all the necessary information. > > Until we have this information, it will be very difficult to help you > further. Should anything change, we would be glad to assist you. Usually private submission of logs (PGP) is acceptable. Note, I am not claiming Xen's `dmesg` contains truly concerning information. The issue is there is enough data for problematic information to unintentionally leak in. Alternatively no pieces would be individually concerning, but all together information may leak. Hopefully ACPI table addresses nor table order are effected by the motherboard serial number, yet those could readily leak information. So far this is acting like a major bug. The paucity of reports is likely due to few people using RAID1 with flash (most people relying greater reliability even before the first large studies came out). -- (\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/) \BS ( | ehem+sigmsg@m5p.com PGP 87145445 | ) / \_CS\ | _____ -O #include O- _____ | / _/ 8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445