LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: linux-integrity@vger.kernel.org
Cc: linux-security-module@vger.kernel.org,
	Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
	Jason Gunthorpe <jgg@ziepe.ca>,
	linux-kernel@vger.kernel.org (open list)
Subject: [PATCH v4 0/4] Migrate all TPM 2.0 commands to use struct tpm_buf
Date: Mon, 26 Mar 2018 15:14:02 +0300	[thread overview]
Message-ID: <20180326121406.14548-1-jarkko.sakkinen@linux.intel.com> (raw)

In order to make struct tpm_buf the first class object for constructing TPM
commands, this patch set migrates all TPM 2.0 commands to use it. Eventually,
tpm_transmit_cmd() can take simply struct tpm_buf as its argument and this
interface can be exported to be used by the kernel keyring and potentially
other subsystems.

The ultimate goal of this work is to make constructing TPM commands inside
the kernel simple and robust.

v4:
* Fixed invalid return value from tpm2_probe(). TPM return codes are
  ignored on purpose as we only care about the tag.
* Removed James' fix for the self test as it was separately applied.

v3:
* Fixed error handling in tpm2_get_random()

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().

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.h      |  19 ++--
 drivers/char/tpm/tpm2-cmd.c | 242 +++++++++++++++++---------------------------
 2 files changed, 105 insertions(+), 156 deletions(-)

-- 
2.15.1

             reply	other threads:[~2018-03-26 12:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-26 12:14 Jarkko Sakkinen [this message]
2018-03-26 12:14 ` [PATCH v4 1/4] tpm: migrate tpm2_shutdown() " Jarkko Sakkinen
2018-05-18  6:29   ` Nayna Jain
2018-05-18 22:30   ` Jerry Snitselaar
2018-05-23 12:56     ` Jarkko Sakkinen
2018-05-27  9:14       ` Jerry Snitselaar
2018-06-05 19:35         ` Jarkko Sakkinen
2018-03-26 12:14 ` [PATCH v4 2/4] tpm: migrate tpm2_probe() " Jarkko Sakkinen
2018-05-18  6:31   ` Nayna Jain
2018-05-18 22:35   ` Jerry Snitselaar
2018-03-26 12:14 ` [PATCH v4 3/4] tpm: migrate tpm2_get_tpm_pt() " Jarkko Sakkinen
2018-05-18  6:31   ` Nayna Jain
2018-05-18  8:05     ` Jarkko Sakkinen
2018-05-18 22:39   ` Jerry Snitselaar
2018-03-26 12:14 ` [PATCH v4 4/4] tpm: migrate tpm2_get_random() " Jarkko Sakkinen
2018-05-18  6:09   ` Nayna Jain
2018-05-18  8:03     ` Jarkko Sakkinen
2018-04-06 10:31 ` [PATCH v4 0/4] Migrate all TPM 2.0 commands " 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=20180326121406.14548-1-jarkko.sakkinen@linux.intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --subject='Re: [PATCH v4 0/4] Migrate all TPM 2.0 commands to use struct tpm_buf' \
    /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

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).