From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Philip Tricca <philip.b.tricca@intel.com>
Cc: Javier Martinez Canillas <javierm@redhat.com>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
"linux-integrity@vger.kernel.org"
<linux-integrity@vger.kernel.org>
Subject: Re: Should we handle TPM_RC_RETRY internally?
Date: Mon, 19 Mar 2018 23:35:36 +0200 [thread overview]
Message-ID: <20180319213536.GG14364@linux.intel.com> (raw)
In-Reply-To: <20180319044056.GD8769@intel.com>
On Sun, Mar 18, 2018 at 09:40:56PM -0700, Philip Tricca wrote:
> I can't say for sure but I'd imagine the implications of implementing a
> retry loop in the kernel are different than user space. We retry
> indefinitely but I would think having some bounded number of retries in
> the kernel would be prudent.
Yes, even if we would support handlig RC_RETRY we could not make promise
to the user space that this error code will never fall through.
/Jarkko
next prev parent reply other threads:[~2018-03-19 21:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-15 18:02 Should we handle TPM_RC_RETRY internally? James Bottomley
2018-03-16 10:36 ` Javier Martinez Canillas
2018-03-16 14:31 ` Jarkko Sakkinen
2018-03-19 4:40 ` Philip Tricca
2018-03-19 21:35 ` Jarkko Sakkinen [this message]
2018-03-16 14:29 ` Jarkko Sakkinen
2018-03-16 15:48 ` James Bottomley
2018-03-19 21:26 ` Jarkko Sakkinen
[not found] ` <CAP7wa8Kq_++HasQY6bZ9idJ_TDOyXhnRAmyUY6t1B+HZWKF8ig@mail.gmail.com>
2018-03-19 21:34 ` Jarkko Sakkinen
2018-03-20 6:06 ` James Bottomley
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=20180319213536.GG14364@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=javierm@redhat.com \
--cc=linux-integrity@vger.kernel.org \
--cc=philip.b.tricca@intel.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 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.