[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <698ceb3b9b35_8c3210068@dwillia2-mobl4.notmuch>
Date: Wed, 11 Feb 2026 12:48:59 -0800
From: <dan.j.williams@...el.com>
To: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@...ux.intel.com>,
<dan.j.williams@...el.com>, "Kirill A . Shutemov" <kas@...nel.org>
CC: Dave Hansen <dave.hansen@...ux.intel.com>, Rick Edgecombe
<rick.p.edgecombe@...el.com>, <x86@...nel.org>,
<linux-kernel@...r.kernel.org>, <linux-coco@...ts.linux.dev>
Subject: Re: [PATCH v1 1/3] virt: tsm: Document size limits for outblob
attributes
Kuppuswamy Sathyanarayanan wrote:
> Hi Dan,
>
> On 2/10/2026 6:15 PM, dan.j.williams@...el.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@...el.com>
> >> Signed-off-by: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@...ux.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?
Given the late date I went ahead and made the change and pushed it out
to start soaking in linux-next:
https://git.kernel.org/pub/scm/linux/kernel/git/devsec/tsm.git/log/?h=next
Powered by blists - more mailing lists