From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "William Brown" <wbrown@suse.de>
Cc: "James Bottomley" <James.Bottomley@HansenPartnership.com>,
<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: Sun, 14 Apr 2024 00:43:22 +0300 [thread overview]
Message-ID: <D0JBMQ8POIZ5.3A7ZIQY5PW9SM@kernel.org> (raw)
In-Reply-To: <C1E92886-E7ED-4425-8A31-22FE196C5218@suse.de>
On Fri Apr 12, 2024 at 2:21 AM EEST, William Brown wrote:
>
>
> > On 12 Apr 2024, at 08:50, Jarkko Sakkinen <jarkko@kernel.org> wrote:
> >
> > On Thu Apr 4, 2024 at 6:49 PM EEST, James Bottomley wrote:
> >> On Thu, 2024-04-04 at 18:09 +0300, Jarkko Sakkinen wrote:
> >>> [...]
> >>> Emphasis that I might have forgotten something but this is what I can
> >>> remember right now.
> >>
> >> What you forgot is that I did originally proposed session degapping in
> >> the kernel resource manager but it was rather complex, so you made me
> >> take it out for lack of a use case. It dates back to when we used the
> >> old sourceforge tpmdd list which seems to have caused message loss, so
> >> I'm not sure how complete this thread is:
> >
> > I might be forgetting some detail to contxt gap but since kernel flushes
> > every single object per transaction contextCounter should be updated all
> > the time and thus there should not be too large gap that would cause
> > emitting this error.
> >
> > I quickly reviewed section 30.5 for architecture specificaton to check
> > if I got it right and it says that: "On receiving this error, the
> > management software either would explicitly flush old session contexts
> > or would load the old session contexts to update their associated
> > counter values.."
>
> The issue is that we *are* flushing session contexts and this error is still occurring.
Was there a way that I could reproduce the same workload or something
simpler that would reproduce the issue on my side?
BR, Jarkko
next prev parent reply other threads:[~2024-04-13 21:43 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 [this message]
2024-04-05 0:24 ` William Brown
2024-04-13 20:54 ` 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=D0JBMQ8POIZ5.3A7ZIQY5PW9SM@kernel.org \
--to=jarkko@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).