linux-kernel - Clarification on SEAM Interface Usage and Patch Scope

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <CA+LcPJ0YQtbYcyyTniFafMOy-iJY++Od1Qd-Tu8vzK7JaFsOLQ@mail.gmail.com>
Date: Sun, 10 Aug 2025 05:50:13 +0500
From: wajahat iqbal <wajahatiqbal22@...il.com>
To: gregkh@...uxfoundation.org
Cc: linux-kernel@...r.kernel.org, 
	Christophe JAILLET <christophe.jaillet@...adoo.fr>
Subject: Clarification on SEAM Interface Usage and Patch Scope

Hi all,

Thanks for the ongoing review and feedback.

To clarify the question about the SEAM interface and whether this
patch should affect multiple drivers:

I performed a thorough search through the kernel source for the term
SEAMCALL to identify all users of the SEAM interface. Running:

=> grep -R "SEAMCALL" .

from the kernel source root revealed that SEAMCALL is currently only
used within the TDX (Intel Trust Domain Extensions) host-side code,
located primarily under:

arch/x86/virt/vmx/tdx/

No other drivers or subsystems in the drivers/ directory or elsewhere
in the kernel tree appear to use this interface.

Therefore, this patch targets the sole existing in-tree consumer of
the SEAM interface. If other uses appear in the future, I am open to
updating them accordingly or submitting follow-up patches.

I will also resend this reply including all previous To: and Cc:
recipients and format it as plain text with inline replies, as
requested.

Please let me know if you have further questions or concerns.

Best regards,
Wajahat Iqbal.