[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <D2GK14M15OCE.XO5Y1ZPO01CG@kernel.org>
Date: Thu, 04 Jul 2024 09:52:16 +0300
From: "Jarkko Sakkinen" <jarkko@...nel.org>
To: "Stefan Berger" <stefanb@...ux.ibm.com>,
<linux-integrity@...r.kernel.org>
Cc: "Thorsten Leemhuis" <regressions@...mhuis.info>, "Linus Torvalds"
<torvalds@...ux-foundation.org>, <stable@...r.kernel.org>, "Peter Huewe"
<peterhuewe@....de>, "Jason Gunthorpe" <jgg@...pe.ca>, "James Bottomley"
<James.Bottomley@...senPartnership.com>, "Mimi Zohar"
<zohar@...ux.ibm.com>, "David Howells" <dhowells@...hat.com>, "Paul Moore"
<paul@...l-moore.com>, "James Morris" <jmorris@...ei.org>, "Serge E.
Hallyn" <serge@...lyn.com>, "Ard Biesheuvel" <ardb@...nel.org>, "Mario
Limonciello" <mario.limonciello@....com>, <linux-kernel@...r.kernel.org>,
<keyrings@...r.kernel.org>, <linux-security-module@...r.kernel.org>
Subject: Re: [PATCH v2 3/3] tpm: Address !chip->auth in
tpm_buf_append_hmac_session*()
On Thu Jul 4, 2024 at 4:56 AM EEST, Stefan Berger wrote:
> [ 1.449673] tpm_ibmvtpm 5000: CRQ initialized
> [ 1.449726] tpm_ibmvtpm 5000: CRQ initialization completed
> [ 2.483218] tpm tpm0: auth session is not active
This expected result and the driver should work as expected.
And it correctly reports that auth session is not active.
The reported error was exactly the TPM errors, which I guess
do not happen anymore.
Reported-by counts as much as reporting the symptom you are
having, i.e. very different from something more "suggestive".
Does that count as tested-by or not?
BR, Jarkko
Powered by blists - more mailing lists