From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: linux-integrity@vger.kernel.org
Cc: linux-security-module@vger.kernel.org, keyrings@vger.kernel.org,
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
Jason Gunthorpe <jgg@ziepe.ca>,
linux-kernel@vger.kernel.org (open list)
Subject: [PATCH v2 0/5] Migrate all TPM 2.0 commands to use struct tpm_buf
Date: Mon, 5 Mar 2018 16:38:58 +0200 [thread overview]
Message-ID: <20180305143904.7477-1-jarkko.sakkinen@linux.intel.com> (raw)
v2:
* Fixed author information in the commit that fixes the self-test issue,
removed '\n' from the log message and added the missing tested-by.
(James: sincere apologies about this)
* Removed the redundant "out of memory" log message from tpm2_shutdown().
* tpm_buf_destroy() was called before using the response data in
tpm2_probe().
* Added missing tpm_buf_destroy() to tpm2_get_random().
James Bottomley (1):
tpm: fix intermittent failure with self tests
Jarkko Sakkinen (4):
tpm: migrate tpm2_shutdown() to use struct tpm_buf
tpm: migrate tpm2_probe() to use struct tpm_buf
tpm: migrate tpm2_get_tpm_pt() to use struct tpm_buf
tpm: migrate tpm2_get_random() to use struct tpm_buf
drivers/char/tpm/tpm-interface.c | 20 ++-
drivers/char/tpm/tpm.h | 20 +--
drivers/char/tpm/tpm2-cmd.c | 281 ++++++++++++++-------------------------
3 files changed, 128 insertions(+), 193 deletions(-)
--
2.15.1
next reply other threads:[~2018-03-05 14:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 14:38 Jarkko Sakkinen [this message]
2018-03-05 14:38 ` [PATCH v2 1/5] tpm: fix intermittent failure with self tests Jarkko Sakkinen
2018-03-05 14:39 ` [PATCH v2 2/5] tpm: migrate tpm2_shutdown() to use struct tpm_buf Jarkko Sakkinen
2018-03-05 14:39 ` [PATCH v2 3/5] tpm: migrate tpm2_probe() " Jarkko Sakkinen
2018-03-05 14:39 ` [PATCH v2 4/5] tpm: migrate tpm2_get_tpm_pt() " Jarkko Sakkinen
2018-03-05 14:39 ` [PATCH v2 5/5] tpm: migrate tpm2_get_random() " 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=20180305143904.7477-1-jarkko.sakkinen@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=jgg@ziepe.ca \
--cc=keyrings@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
/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
all inboxes | Powered by JetHome®