From: Laurent Bigonville <bigon@debian.org>
To: linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
Peter Huewe <peterhuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>
Subject: Re: [PATCH] tpm_tis: verify locality released before returning from release_locality
Date: Thu, 10 May 2018 13:21:39 +0200 [thread overview]
Message-ID: <e2d0e88a-d4b7-9a4e-45c5-b2409d6c6cab@debian.org> (raw)
In-Reply-To: <20180505200315.x7jt33j7psizmfyi@cantor>
Le 05/05/18 à 22:03, Jerry Snitselaar a écrit :
> On Sat May 05 18, Jerry Snitselaar wrote:
>> [...]
>>
>
> Laurent,
Hello Jerry,
> Can you try this patch with your system since it is the one
> that has exhibited the problem so far. I've tested on a
> tpm2.0 and tpm1.2 system here.
I just tested the patch and the driver is loading fine again and the
device in /dev is present again, so it seems to work.
But for some reason the tpm is again locked (for no visible reason) due
to "dictionary attack" so I cannot test further ATM :/
Regards,
Laurent
>
> Regards,
> Jerry
WARNING: multiple messages have this Message-ID (diff)
From: Laurent Bigonville <bigon@debian.org>
To: linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
Peter Huewe <peterhuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>
Subject: Re: [PATCH] tpm_tis: verify locality released before returning from release_locality
Date: Thu, 10 May 2018 13:21:39 +0200 [thread overview]
Message-ID: <e2d0e88a-d4b7-9a4e-45c5-b2409d6c6cab@debian.org> (raw)
In-Reply-To: <20180505200315.x7jt33j7psizmfyi@cantor>
Le 05/05/18 a 22:03, Jerry Snitselaar a ecrit :
> On Sat May 05 18, Jerry Snitselaar wrote:
>> [...]
>>
>
> Laurent,
Hello Jerry,
> Can you try this patch with your system since it is the one
> that has exhibited the problem so far. I've tested on a
> tpm2.0 and tpm1.2 system here.
I just tested the patch and the driver is loading fine again and the
device in /dev is present again, so it seems to work.
But for some reason the tpm is again locked (for no visible reason) due
to "dictionary attack" so I cannot test further ATM :/
Regards,
Laurent
>
> Regards,
> Jerry
next prev parent reply other threads:[~2018-05-10 11:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-05 19:54 [PATCH] tpm_tis: verify locality released before returning from release_locality Jerry Snitselaar
2018-05-05 20:03 ` Jerry Snitselaar
2018-05-10 11:21 ` Laurent Bigonville [this message]
2018-05-10 11:21 ` Laurent Bigonville
2018-05-11 10:19 ` Jarkko Sakkinen
2018-05-11 10:19 ` Jarkko Sakkinen
2018-05-11 19:02 ` Laurent Bigonville
2018-05-11 19:02 ` Laurent Bigonville
2018-05-28 8:44 ` Laurent Bigonville
2018-05-28 8:44 ` Laurent Bigonville
2018-05-28 9:01 ` Jerry Snitselaar
2018-05-28 9:01 ` Jerry Snitselaar
2018-05-14 10:27 ` Jarkko Sakkinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e2d0e88a-d4b7-9a4e-45c5-b2409d6c6cab@debian.org \
--to=bigon@debian.org \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.