From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "William Brown" <wbrown@suse.de>
Cc: <linux-integrity@vger.kernel.org>, <peterhuewe@gmx.de>,
<jgg@ziepe.ca>, "Takashi Iwai" <tiwai@suse.de>
Subject: Re: TPM error 0x0901, possibly related to TPM2_PT_CONTEXT_GAP_MAX
Date: Sat, 13 Apr 2024 23:54:59 +0300 [thread overview]
Message-ID: <D0JALOP2RDHA.21T8JRY0LWKN2@kernel.org> (raw)
In-Reply-To: <F34D4DB5-EDFF-4E04-A35D-D9044F513A99@suse.de>
On Fri Apr 5, 2024 at 3:24 AM EEST, William Brown wrote:
>
>
> > On 5 Apr 2024, at 01:06, Jarkko Sakkinen <jarkko@kernel.org> wrote:
> >
> > Since the code is accessing /dev/tpm0 and not /dev/tpmrm0 this issue
> > should be mitigated by the user space resource manager.
>
> My code is operating via /dev/tpmrm0, not /dev/tpm0. And after each iteration, all sessions are cleared and removed.
>
> If I operate on /dev/tpm0 the issue goes away. So the error is actually in the resource manager itself.
Ah, my previous response about kprobe hook is still relevant.
Kernel RM can cause context gap error if user space leaves a
stall session long enough. Before making any decisions we should
be aware first what are the exact conditions in this case.
Sorry for late response. I was sick for most of last wee.
BR, Jarkko
prev parent reply other threads:[~2024-04-13 20:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 2:19 TPM error 0x0901, possibly related to TPM2_PT_CONTEXT_GAP_MAX William Brown
2024-04-04 15:06 ` Jarkko Sakkinen
2024-04-04 15:09 ` Jarkko Sakkinen
2024-04-04 15:49 ` James Bottomley
2024-04-05 0:24 ` William Brown
2024-04-13 20:50 ` Jarkko Sakkinen
2024-04-11 22:50 ` Jarkko Sakkinen
2024-04-11 23:21 ` William Brown
2024-04-13 21:43 ` Jarkko Sakkinen
2024-04-05 0:24 ` William Brown
2024-04-13 20:54 ` Jarkko Sakkinen [this message]
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=D0JALOP2RDHA.21T8JRY0LWKN2@kernel.org \
--to=jarkko@kernel.org \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=tiwai@suse.de \
--cc=wbrown@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox