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,
	Jason Gunthorpe <jgg@ziepe.ca>,
	open list <linux-kernel@vger.kernel.org>,
	tomas.winkler@intel.com,
	James Bottomley <James.Bottomley@HansenPartnership.com>
Subject: Re: [PATCH v4 0/4] Migrate all TPM 2.0 commands to use struct tpm_buf
Date: Fri, 6 Apr 2018 13:31:01 +0300	[thread overview]
Message-ID: <20180406103101.GA14379@linux.intel.com> (raw)
In-Reply-To: <20180326121406.14548-1-jarkko.sakkinen@linux.intel.com>

On Mon, Mar 26, 2018 at 03:14:02PM +0300, Jarkko Sakkinen wrote:
> 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.

I pushed these commits to the master branch. Please report if you have
any issues. If the master branch continues working for you, as you test
it maybe for other reasons, I'm happy to get tested-by's for them. At
worst they have regressions. I seriously don't think that the code
changes have any major structural issues.

I would guess that Tomas' similar changes for TPM 1.x will follow at
some point. I'm looking forward to change the existing tpm_send()
as one that takes tpm_buf in. That will allow to remove a lot of
cruft code from keyring.

I take no rush to merge these to 'next' but I think it is fine to
have these in the bleeding edge.

/Jarkko

      parent reply	other threads:[~2018-04-06 10:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-26 12:14 Jarkko Sakkinen
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 ` Jarkko Sakkinen [this message]

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=20180406103101.GA14379@linux.intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=tomas.winkler@intel.com \
    --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).