Re: [RFC PATCH v1 03/11] attestation: Enter secure operation when evidence is accepted

Jiri Pirko [off-list ref] writes:

Wed, Oct 28, 2026 at 04:26:10PM +0100, aneesh.kumar@kernel.org wrote:

quoted

Use EVIDENCE_ACCEPT to enter secure operation after userspace has
checked the evidence. Check the referenced device and evidence
generations before calling the driver, and record acceptance on success.

Remove the separate DEVSEC_RUN command and callback.

Keep DEVSEC_STATE_GET so userspace can read both evidence acceptance and
device state. Clearing acceptance does not undo the device state change.
For example, with the following PCI/TSM patches:

Note that the published wip_attestation_all_1 baseline still
has DEVSEC_RUN. I am planning this merge into EVIDENCE_ACCEPT for
my next revision, which is not pushed yet.

I agree with your comments here and in the other emails regarding
attestation. I will wait for the next revision of your attestation
series. If you can accommodate these changes there, I can rework my
patches accordingly.

Could you also add the ctlv-attestation-spdm family so that I can base
the PCI/TSM changes on top of it?

-aneesh