linux-kernel - Re: [PATCH v5] virt: tdx-guest: Handle GetQuote request error code

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <56c01575-c0e3-43f3-a6c6-bf62fcbe4f5d@intel.com>
Date: Tue, 2 Dec 2025 16:03:45 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@...ux.intel.com>,
 "Kirill A . Shutemov" <kas@...nel.org>
Cc: Rick Edgecombe <rick.p.edgecombe@...el.com>,
 Dave Hansen <dave.hansen@...ux.intel.com>,
 Dan Williams <dan.j.williams@...el.com>, x86@...nel.org,
 linux-kernel@...r.kernel.org, linux-coco@...ts.linux.dev
Subject: Re: [PATCH v5] virt: tdx-guest: Handle GetQuote request error code

On 12/2/25 16:00, Kuppuswamy Sathyanarayanan wrote:
> The reason the kernel must parse the status field is that the failure
> code is only available in the header portion of the shared GPA buffer
> populated by the VMM. Userspace currently does not have access to this
> header since we only expose the Quote payload itself. Because userspace
> cannot directly interpret the VMM status codes, the kernel needs to parse
> them and return appropriate generic error codes.

That's kinda the key to this.

Users are poking at sysfs and expect (near) universal explicit errors.
Are they even doing this from shell scripts most of the time?

Also, please don't just keep tacking gunk onto the changelog. Start
cutting out the cruft, please.