[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e939739d-d193-95e8-c142-4efa57be2502@gmail.com>
Date: Wed, 27 May 2020 21:40:25 -0700
From: Tadeusz Struk <tstruk@...il.com>
To: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
Cc: James Bottomley <James.Bottomley@...senPartnership.com>,
Mario Limonciello <mario.limonciello@...l.com>,
Peter Huewe <peterhuewe@....de>,
Jason Gunthorpe <jgg@...pe.ca>, Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-integrity@...r.kernel.org, linux-kernel@...r.kernel.org,
Jeffrin Jose T <jeffrin@...agiritech.edu.in>,
Alex Guzman <alex@...man.io>
Subject: Re: [PATCH] tpm: Revert "tpm: fix invalid locking in NONBLOCKING
mode"
On 5/27/20 5:30 PM, Jarkko Sakkinen wrote:
>> This won't help if the message is read by an async tcti. If the problem lies
>> in the chip get locality code, perhaps this could help to debug the root-cause
>> instead of masking it out in the upper layer code:
> What is TCTI and async TCTI? Not following.
TPM Command Transmission Interface (TCTI) as defined by TCG in
https://trustedcomputinggroup.org/resource/tss-tcti-specification/
the reason we added the O_NONBLOCK mode was to satisfy the TCG spec for async TCTI.
Thanks,
Tadeusz
Powered by blists - more mailing lists