[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190830143852.GA302@ziepe.ca>
Date: Fri, 30 Aug 2019 11:38:52 -0300
From: Jason Gunthorpe <jgg@...pe.ca>
To: Seunghun Han <kkamagui@...il.com>
Cc: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>,
Peter Huewe <peterhuewe@....de>,
"open list:TPM DEVICE DRIVER" <linux-integrity@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/2] tpm: tpm_crb: enhance resource mapping mechanism for
supporting AMD's fTPM
On Fri, Aug 30, 2019 at 10:54:59PM +0900, Seunghun Han wrote:
> When I tested this patch in my machine, it seemed that ACPI NVS was
> saved after TPM CRB driver sent "TPM2_Shutdown(STATE)" to the fTPM
> while suspending. Then, ACPI NVS was restored while resuming.
> After resuming, PCRs didn't change and TPM2 tools such as
> tpm2_pcrlist, tpm2_extend, tpm2_getrandoms worked well.
> So, according to my test result, it seems that the patch doesn't
> create bugs and race during resume.
I have a feeling that is shear luck of link time ordering and not guarenteed??
Jason
Powered by blists - more mailing lists