From: Sumit Garg <sumit.garg@linaro.org>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: dhowells@redhat.com, peterhuewe@gmx.de, keyrings@vger.kernel.org,
linux-integrity@vger.kernel.org,
"open list:HARDWARE RANDOM NUMBER GENERATOR CORE"
<linux-crypto@vger.kernel.org>,
linux-security-module@vger.kernel.org,
Herbert Xu <herbert@gondor.apana.org.au>,
davem@davemloft.net, jgg@ziepe.ca, Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
jejb@linux.ibm.com, Mimi Zohar <zohar@linux.ibm.com>,
James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Daniel Thompson <daniel.thompson@linaro.org>
Subject: Re: [Patch v7 0/4] Create and consolidate trusted keys subsystem
Date: Tue, 15 Oct 2019 14:02:15 +0530 [thread overview]
Message-ID: <CAFA6WYM1AfYfk1+eJeDJeaRddF7kQ8mi+-DKbcND1gkOzkF6=Q@mail.gmail.com> (raw)
In-Reply-To: <20191014201604.GN15552@linux.intel.com>
On Tue, 15 Oct 2019 at 01:46, Jarkko Sakkinen
<jarkko.sakkinen@linux.intel.com> wrote:
>
> On Fri, Oct 11, 2019 at 02:05:17PM -0700, Jerry Snitselaar wrote:
> > On Fri Oct 11 19, Jarkko Sakkinen wrote:
> > > On Mon, Oct 07, 2019 at 10:55:31AM +0530, Sumit Garg wrote:
> > > > This patch-set does restructuring of trusted keys code to create and
> > > > consolidate trusted keys subsystem.
> > > >
> > > > Also, patch #2 replaces tpm1_buf code used in security/keys/trusted.c and
> > > > crypto/asymmertic_keys/asym_tpm.c files to use the common tpm_buf code.
> > > >
> > > > Changes in v7:
> > > > 1. Rebased to top of tpmdd/master
> > > > 2. Patch #4: update tpm2 trusted keys code to use tpm_send() instead of
> > > > tpm_transmit_cmd() which is an internal function.
> > > >
> > > > Changes in v6:
> > > > 1. Switch TPM asymmetric code also to use common tpm_buf code. These
> > > > changes required patches #1 and #2 update, so I have dropped review
> > > > tags from those patches.
> > > > 2. Incorporated miscellaneous comments from Jarkko.
> > > >
> > > > Changes in v5:
> > > > 1. Drop 5/5 patch as its more relavant along with TEE patch-set.
> > > > 2. Add Reviewed-by tag for patch #2.
> > > > 3. Fix build failure when "CONFIG_HEADER_TEST" and
> > > > "CONFIG_KERNEL_HEADER_TEST" config options are enabled.
> > > > 4. Misc changes to rename files.
> > > >
> > > > Changes in v4:
> > > > 1. Separate patch for export of tpm_buf code to include/linux/tpm.h
> > > > 2. Change TPM1.x trusted keys code to use common tpm_buf
> > > > 3. Keep module name as trusted.ko only
> > > >
> > > > Changes in v3:
> > > >
> > > > Move TPM2 trusted keys code to trusted keys subsystem.
> > > >
> > > > Changes in v2:
> > > >
> > > > Split trusted keys abstraction patch for ease of review.
> > > >
> > > > Sumit Garg (4):
> > > > tpm: Move tpm_buf code to include/linux/
> > > > KEYS: Use common tpm_buf for trusted and asymmetric keys
> > > > KEYS: trusted: Create trusted keys subsystem
> > > > KEYS: trusted: Move TPM2 trusted keys code
> > > >
> > > > crypto/asymmetric_keys/asym_tpm.c | 101 +++----
> > > > drivers/char/tpm/tpm-interface.c | 56 ----
> > > > drivers/char/tpm/tpm.h | 226 ---------------
> > > > drivers/char/tpm/tpm2-cmd.c | 307 --------------------
> > > > include/Kbuild | 1 -
> > > > include/keys/{trusted.h => trusted_tpm.h} | 49 +---
> > > > include/linux/tpm.h | 251 ++++++++++++++--
> > > > security/keys/Makefile | 2 +-
> > > > security/keys/trusted-keys/Makefile | 8 +
> > > > .../{trusted.c => trusted-keys/trusted_tpm1.c} | 96 +++----
> > > > security/keys/trusted-keys/trusted_tpm2.c | 314 +++++++++++++++++++++
> > > > 11 files changed, 652 insertions(+), 759 deletions(-)
> > > > rename include/keys/{trusted.h => trusted_tpm.h} (77%)
> > > > create mode 100644 security/keys/trusted-keys/Makefile
> > > > rename security/keys/{trusted.c => trusted-keys/trusted_tpm1.c} (94%)
> > > > create mode 100644 security/keys/trusted-keys/trusted_tpm2.c
> > > >
> > > > --
> > > > 2.7.4
> > > >
> > >
> > > I fixed a merge conflict caused by James' commit. Already pushed.
> > > Compiling test kernel ATM i.e. tested-by's will follow later.
> > >
> > > /Jarkko
> >
> > Are you missing patch 4 on master?
>
> Already removed the patch set given the sparse issues.
The sparse issues weren't due to this patch-set but they already
existed in "security/keys/trusted.c" and this patch-set only did a
rename for that file. So I think we should have a separate patch to
fix sparse issues.
-Sumit
> Read this email
> after doing that. Thanks anyway for pointing that out.
>
> /Jarkko
next prev parent reply other threads:[~2019-10-15 8:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 5:25 [Patch v7 0/4] Create and consolidate trusted keys subsystem Sumit Garg
2019-10-07 5:25 ` [Patch v7 1/4] tpm: Move tpm_buf code to include/linux/ Sumit Garg
2019-10-11 11:41 ` Jarkko Sakkinen
2019-10-11 22:33 ` Jerry Snitselaar
2019-10-07 5:25 ` [Patch v7 2/4] KEYS: Use common tpm_buf for trusted and asymmetric keys Sumit Garg
2019-10-11 11:47 ` Jarkko Sakkinen
2019-10-11 22:34 ` Jerry Snitselaar
2019-10-07 5:25 ` [Patch v7 3/4] KEYS: trusted: Create trusted keys subsystem Sumit Garg
2019-10-07 5:25 ` [Patch v7 4/4] KEYS: trusted: Move TPM2 trusted keys code Sumit Garg
2019-10-11 12:25 ` Jarkko Sakkinen
2019-10-11 12:37 ` [Patch v7 0/4] Create and consolidate trusted keys subsystem Jarkko Sakkinen
2019-10-11 21:05 ` Jerry Snitselaar
2019-10-14 20:16 ` Jarkko Sakkinen
2019-10-15 8:32 ` Sumit Garg [this message]
2019-10-14 19:33 ` Jarkko Sakkinen
2019-10-15 8:28 ` Sumit Garg
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='CAFA6WYM1AfYfk1+eJeDJeaRddF7kQ8mi+-DKbcND1gkOzkF6=Q@mail.gmail.com' \
--to=sumit.garg@linaro.org \
--cc=arnd@arndb.de \
--cc=daniel.thompson@linaro.org \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jejb@linux.ibm.com \
--cc=jgg@ziepe.ca \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=serge@hallyn.com \
--cc=zohar@linux.ibm.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).