From: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
To: dan.j.williams@intel.com, "Kirill A . Shutemov" <kas@kernel.org>
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
Rick Edgecombe <rick.p.edgecombe@intel.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
linux-coco@lists.linux.dev
Subject: Re: [PATCH v1 1/3] virt: tsm: Document size limits for outblob attributes
Date: Wed, 11 Feb 2026 08:40:46 -0800 [thread overview]
Message-ID: <163b74e8-eede-4872-9319-047db25c0050@linux.intel.com> (raw)
In-Reply-To: <698be62f7802_8c32100e2@dwillia2-mobl4.notmuch>
Hi Dan,
On 2/10/2026 6:15 PM, dan.j.williams@intel.com wrote:
> Kuppuswamy Sathyanarayanan wrote:
>> The configfs-tsm-report interface can fail with -EFBIG when the
>> attestation report generated by a TSM provider exceeds internal
>> maximums (TSM_REPORT_OUTBLOB_MAX). However, this error condition and
>> its handling are not currently documented in the ABI.
>>
>> Userspace tools need to understand how to interpret various error
>> conditions when reading attestation reports.
>>
>> Document that reads fail with -EFBIG when reports exceed size limits,
>> with guidance on how to resolve them.
>>
>> Reviewed-by: Fang Peter <peter.fang@intel.com>
>> Signed-off-by: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
>
> Looks good, I will change the subject to:
>
> "configfs-tsm-report: Document size limits for outblob attributes"
Thanks for the review! Are you planning to apply this with the updated
subject line, or would you like me to send a v2 with the change?
--
Sathyanarayanan Kuppuswamy
Linux Kernel Developer
next prev parent reply other threads:[~2026-02-11 16:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 0:17 [PATCH v1 0/3] Increase CoCo attestation report buffer size Kuppuswamy Sathyanarayanan
2026-02-11 0:17 ` [PATCH v1 1/3] virt: tsm: Document size limits for outblob attributes Kuppuswamy Sathyanarayanan
2026-02-11 2:15 ` dan.j.williams
2026-02-11 16:40 ` Kuppuswamy Sathyanarayanan [this message]
2026-02-11 20:48 ` dan.j.williams
2026-02-11 0:17 ` [PATCH v1 2/3] virt: tsm: Increase TSM_REPORT_OUTBLOB_MAX to 16MB Kuppuswamy Sathyanarayanan
2026-02-11 2:16 ` dan.j.williams
2026-02-11 0:17 ` [PATCH v1 3/3] virt: tdx-guest: Increase Quote buffer size to 128KB Kuppuswamy Sathyanarayanan
2026-02-11 2:19 ` dan.j.williams
2026-02-11 11:17 ` Kiryl Shutsemau
2026-02-11 18:40 ` Kuppuswamy Sathyanarayanan
2026-02-11 21:06 ` dan.j.williams
2026-02-11 21:13 ` Kuppuswamy Sathyanarayanan
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=163b74e8-eede-4872-9319-047db25c0050@linux.intel.com \
--to=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=kas@kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=rick.p.edgecombe@intel.com \
--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