From: Peter Fang <peter.fang@intel.com>
To: Kiryl Shutsemau <kas@kernel.org>
Cc: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>,
"Hansen, Dave" <dave.hansen@intel.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"bp@alien8.de" <bp@alien8.de>,
"Li, Xiaoyao" <xiaoyao.li@intel.com>,
"x86@kernel.org" <x86@kernel.org>,
"sathyanarayanan.kuppuswamy@linux.intel.com"
<sathyanarayanan.kuppuswamy@linux.intel.com>,
"mingo@redhat.com" <mingo@redhat.com>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"tglx@kernel.org" <tglx@kernel.org>,
"linux-coco@lists.linux.dev" <linux-coco@lists.linux.dev>,
"hpa@zytor.com" <hpa@zytor.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"binbin.wu@linux.intel.com" <binbin.wu@linux.intel.com>
Subject: Re: [PATCH v2 2/2] virt: tdx-guest: Allocate Quote buffer dynamically
Date: Thu, 23 Jul 2026 01:19:46 -0700 [thread overview]
Message-ID: <20260723081946.GA482062@pedri> (raw)
In-Reply-To: <amCv00f5Q6QlztyY@thinkstation>
On Wed, Jul 22, 2026 at 01:00:35PM +0100, Kiryl Shutsemau wrote:
> On Tue, Jul 21, 2026 at 04:43:57PM +0000, Edgecombe, Rick P wrote:
> > BUT, is this number coming from the untrusted host or the TDX module? I cant
> > find TDCS_QUOTE_MAX_SIZE in the docs.
>
> I cannot find it too. Peter, any pointers where it is documented
> publicly?
Gosh sorry I missed this. Turns out it was not fully published due to
some internal error. Yikes.
This metadata field is documented in "Intel TDX Module Extension for
Quoting", Section "TD-Scope Metadata" [1]. But the encoding of this
field got missed in the June 2026 release of "Intel TDX Module ABI
Definitions". I just escalated this. I'll come back and give an update
once it's fixed... Apologies for the oversight.
[1] https://cdrdv2.intel.com/v1/dl/getContent/874303
>
> > If it is coming from the TDX module then
> > we are not talking about security considerations at all. It's just a functional
> > "do you want to know if things are failing". Not sure why this one would be
> > special in that regard. If we think it will fail so often that we don't want a
> > warning, then we probably need another solution.
>
> Silent makes no sense to me. We are talking about attestation. If
> attestation fails the TD is functionally dead: it cannot obtain secrets.
Yep. I'll remove __GFP_NOWARN in the next version. Thanks.
>
> --
> Kiryl Shutsemau / Kirill A. Shutemov
next prev parent reply other threads:[~2026-07-23 8:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 21:43 [PATCH v2 0/2] tdx-guest: Make Quote buffer size dynamic Peter Fang
2026-07-17 21:43 ` [PATCH v2 1/2] x86/tdx: Add helper to query maximum TD Quote size Peter Fang
2026-07-22 13:21 ` Binbin Wu
2026-07-17 21:43 ` [PATCH v2 2/2] virt: tdx-guest: Allocate Quote buffer dynamically Peter Fang
2026-07-20 13:35 ` Dave Hansen
2026-07-21 6:49 ` Peter Fang
2026-07-21 13:48 ` Dave Hansen
2026-07-21 16:43 ` Edgecombe, Rick P
2026-07-22 7:36 ` Peter Fang
2026-07-22 12:00 ` Kiryl Shutsemau
2026-07-23 8:19 ` Peter Fang [this message]
2026-07-22 6:39 ` Peter Fang
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=20260723081946.GA482062@pedri \
--to=peter.fang@intel.com \
--cc=binbin.wu@linux.intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kas@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rick.p.edgecombe@intel.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=tglx@kernel.org \
--cc=x86@kernel.org \
--cc=xiaoyao.li@intel.com \
/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