From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Martin Galvan <omgalvan.86@gmail.com>
Cc: linux-integrity@vger.kernel.org
Subject: Re: Question about the TPM driver
Date: Sun, 16 Sep 2018 22:16:05 +0300 [thread overview]
Message-ID: <20180916191605.GB7473@linux.intel.com> (raw)
In-Reply-To: <CAN19L9EEYK+OpJSCw+nNv7fCjkS5eQeAXfy=51nfk=fBZne-BA@mail.gmail.com>
On Thu, Sep 13, 2018 at 10:14:30AM -0300, Martin Galvan wrote:
> Hi all,
>
> I noticed that, after a command is done, the TPM driver only allows
> for a single read operation (for a limited time). If I wanted to e.g.
> check a command's response code before attempting to read the rest of
> the response, my next read would fail. Same happens if I take too long
> to read a command's results.
>
> I can understand the timeout, but I'm curious about this single-read
> policy, especially since some commands such as GetCapability don't
> guarantee how much data will actually be returned. Does anyone know
> why it was implemented this way?
>
> Thanks
I understand your concerns but without a concrete workload there is no
problem with this behavior.
/Jarkko
next prev parent reply other threads:[~2018-09-17 0:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 13:14 Question about the TPM driver Martin Galvan
2018-09-13 14:22 ` James Bottomley
2018-09-13 14:31 ` Martin Galvan
2018-09-13 15:11 ` Javier Martinez Canillas
2018-09-13 15:21 ` Tadeusz Struk
2018-09-13 15:26 ` Martin Galvan
2018-10-11 15:17 ` Ken Goldman
2018-09-16 19:16 ` Jarkko Sakkinen [this message]
2018-09-17 13:32 ` Martin Galvan
2018-09-17 14:45 ` James Bottomley
2018-09-17 21:23 ` Jarkko Sakkinen
2018-09-17 21:20 ` 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=20180916191605.GB7473@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=linux-integrity@vger.kernel.org \
--cc=omgalvan.86@gmail.com \
/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 NNTP newsgroup(s).