[tpm2] Re: tpm2_flushcontext stuck

When /dev/tpmrm0 was used with kernel 5.10.
After sending the command read public:
0x80 0x01 0x00 0x00 0x00 0x0e 0x00 0x00 0x01 0x73 0x80 0x00 0x00 0x00
the write worked but the poll call in  tcti_device_receive did stuck.
With kernel 4.19 write for this command did return -1



Am 20.12.21 um 21:04 schrieb Kenneth Goldman:
> They way I use it:
> 
>  
> 
> /dev/tpm0 is locking, one user at a time.  I use it for debug only.  IMHO, production applications should not use it.
> 
>  
> 
> /dev/tpmrm0 is the multi-user interface.  Use it for production applications, where the TPM is shared.
> 
>  
> 
> I suspect (not sure) that /dev/tpm0 will have unexpected effects when the kernel is also trying to use the TPM.
> 
>  
> 
>  
> 
> And as a newbie, I felt that the fact TPM exposes two devices (/dev/tpm0 and /dev/tpmrm0) under Linux is confusing and is making things more complicated.  The architecture diagram (https://github.com/tpm2-software/tpm2-tss <https://github.com/tpm2-software/tpm2-tss>) shows all calls go through the Resource Manager but that is not the case in reality.  I was wondering what is the benefit to have 2 devices instead of just one device in linux? 
> 
>  
> 
> 
> _______________________________________________
> tpm2 mailing list -- tpm2(a)lists.01.org
> To unsubscribe send an email to tpm2-leave(a)lists.01.org
> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
>