Re: [PATCH 1/3] tpm: protect against locality counter underflow

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2/20/24 2:26 PM, Jarkko Sakkinen wrote:
On Tue Feb 20, 2024 at 8:54 PM UTC, Lino Sanfilippo wrote:
for (i = 0; i <= MAX_LOCALITY; i++)
	__tpm_tis_relinquish_locality(priv, i);

I'm pretty unfamiliar with Intel TXT so asking a dummy question:
if Intel TXT uses locality 2 I suppose we should not try to
relinquish it, or?

The TPM has five localities (0 - 4). Localities 1 - 4 are for DRTM support. For TXT, locality 4 is hard wired to the CPU - nothing else can touch it. Locality 3 is only ever accessible when the CPU is executing an AC (Authenticated Code) module. That leaves 1 and 2 for the DRTM software environment to use. If the DRTM software opens 1 or 2, it should close them before exiting the DRTM.


AFAIK, we don't have a symbol called MAX_LOCALITY.

Daniel added it in the patch set.

Thanks
Ross


BR, Jarkko





[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Linux Kernel]     [Linux Kernel Hardening]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux SCSI]

  Powered by Linux