From nobody Thu Apr 2 17:22:44 2026 Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 4817717C203 for ; Wed, 11 Feb 2026 00:17:36 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=192.198.163.10 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770769057; cv=none; b=Yi4B3cMMGgmaxAdgbuZlTZHrE1wKKd2/78LgP8I5MzVXRo3jii8hJZdiG6POK3HbIoPAx6ewc5GnOcTVnwFOHXKlvImuFmxMsMmZDCxuMdxMeyRi0tmEpjwEE/XBN7u8Ss8hThuRk9M9ZiFaYGble3kuMPaL47HpPv7v3kxNuhI= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770769057; c=relaxed/simple; bh=GWbPa0IQdLEfy+oY9pM1KUhEV2z9oXrVQSeSsl3oXCA=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=YJUJKyzg7CT+imqf1D3tW4thbAY/KhyvqcTKdLrxEsFdD5xgTL5X2WWqIvOXQ7/HIXd9nv9SF5LXA4Sm40WsqQj2s+BitaPoR5n07pKhX0L30KQOcJi32YktOHNUiUP+8+yQw167E6c6qKHAoUQVNwBoDFhuEJ/7DUICgsRkMDA= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com; spf=pass smtp.mailfrom=linux.intel.com; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b=lqEhZ10f; arc=none smtp.client-ip=192.198.163.10 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.intel.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b="lqEhZ10f" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1770769056; x=1802305056; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=GWbPa0IQdLEfy+oY9pM1KUhEV2z9oXrVQSeSsl3oXCA=; b=lqEhZ10fYwhDS7NwBQdQOvZbMVl/royP9ggQNA8KGJMHYPMlFn86SBKY q/WsKWDYDtjUVsiFE3Rk5pVZD0/bd07MPDAA0wQwr7WmEOYG5Vl69juIb 8vzyKPWZ8Ezpr5z1A9ORsmVqrWoNLqM/8xM527PJQZIbakd+vWTlvXPDh NtvFQM/DU9yorj7xNS+Qdxr9g4JKb4tIuDW+dIGfjebkOwZDgD9cgZva5 rFU9SbF+8Mfzing5nDm6FVa1fKeemJ5AB+Dr/u6zzQQ9UxXw6TZf49brI fk/ugrVdyOB+mI7qpE4bgK40yuUNYukt5p0sQurDnj0Y7gFMTgGgXfPAZ A==; X-CSE-ConnectionGUID: YyVKuxIKSm+lVJenHh3Jfg== X-CSE-MsgGUID: /j+1D75ATQmXLP3p5Y9FFw== X-IronPort-AV: E=McAfee;i="6800,10657,11697"; a="83279905" X-IronPort-AV: E=Sophos;i="6.21,283,1763452800"; d="scan'208";a="83279905" Received: from orviesa003.jf.intel.com ([10.64.159.143]) by fmvoesa104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 10 Feb 2026 16:17:31 -0800 X-CSE-ConnectionGUID: bK7XIxJzSDaGYQN8eM5SAA== X-CSE-MsgGUID: 80sUtp13SU2jptDOUWO1ow== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.21,283,1763452800"; d="scan'208";a="216242052" Received: from skuppusw-desk2.jf.intel.com ([10.165.154.101]) by ORVIESA003-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 10 Feb 2026 16:17:31 -0800 From: Kuppuswamy Sathyanarayanan To: Dan Williams , "Kirill A . Shutemov" Cc: Dave Hansen , Rick Edgecombe , x86@kernel.org, linux-kernel@vger.kernel.org, linux-coco@lists.linux.dev Subject: [PATCH v1 1/3] virt: tsm: Document size limits for outblob attributes Date: Tue, 10 Feb 2026 16:17:10 -0800 Message-ID: <20260211001712.1531955-2-sathyanarayanan.kuppuswamy@linux.intel.com> X-Mailer: git-send-email 2.43.0 In-Reply-To: <20260211001712.1531955-1-sathyanarayanan.kuppuswamy@linux.intel.com> References: <20260211001712.1531955-1-sathyanarayanan.kuppuswamy@linux.intel.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" 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 Signed-off-by: Kuppuswamy Sathyanarayanan --- Documentation/ABI/testing/configfs-tsm-report | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/Documentation/ABI/testing/configfs-tsm-report b/Documentation/= ABI/testing/configfs-tsm-report index 534408bc1408..ca3352cfd2f1 100644 --- a/Documentation/ABI/testing/configfs-tsm-report +++ b/Documentation/ABI/testing/configfs-tsm-report @@ -17,6 +17,12 @@ Description: where the implementation is conveyed via the @provider attribute. =20 + This interface fails reads and sets errno to EFBIG when the + report generated by @provider exceeds the configfs-tsm-report + internal maximums. Contact the platform provider for the + compatible security module, driver, and attestation library + combination. + What: /sys/kernel/config/tsm/report/$name/auxblob Date: October, 2023 KernelVersion: v6.7 @@ -31,6 +37,9 @@ Description: Standardization v2.03 Section 4.1.8.1 MSG_REPORT_REQ. https://www.amd.com/content/dam/amd/en/documents/epyc-technical-docs/spe= cifications/56421.pdf =20 + See "EFBIG" comment in the @outblob description for potential + error conditions. + What: /sys/kernel/config/tsm/report/$name/manifestblob Date: January, 2024 KernelVersion: v6.10 @@ -43,6 +52,9 @@ Description: See 'service_provider' for information on the format of the manifest blob. =20 + See "EFBIG" comment in the @outblob description for potential + error conditions. + What: /sys/kernel/config/tsm/report/$name/provider Date: September, 2023 KernelVersion: v6.7 --=20 2.43.0