From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Cc: linux-integrity@vger.kernel.org,
linux-security-module@vger.kernel.org,
Matt Mackall <mpm@selenic.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Peter Huewe <peterhuewe@gmx.de>,
Marcel Selhorst <tpmdd@selhorst.net>,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
Dmitry Kasatkin <dmitry.kasatkin@gmail.com>,
James Morris <james.l.morris@oracle.com>,
"Serge E. Hallyn" <serge@hallyn.com>,
David Howells <dhowells@redhat.com>,
Jerry Snitselaar <jsnitsel@redhat.com>,
"open list:HARDWARE RANDOM NUMBER GENERATOR CORE"
<linux-crypto@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"open list:KEYS-TRUSTED" <keyrings@vger.kernel.org>
Subject: Re: [PATCH] tpm: remove chip_num parameter from in-kernel API
Date: Tue, 24 Oct 2017 22:27:41 +0000 [thread overview]
Message-ID: <20171024222741.lqvgpdaosjazpvfd@linux.intel.com> (raw)
In-Reply-To: <20171024185208.GD1806@obsidianresearch.com>
On Tue, Oct 24, 2017 at 12:52:08PM -0600, Jason Gunthorpe wrote:
> On Mon, Oct 23, 2017 at 02:38:14PM +0200, Jarkko Sakkinen wrote:
> > The reasoning is simple and obvious. Since every call site passes the
> > value TPM_ANY_NUM (0xFFFF) the parameter does not have right to exist.
> > Refined the documentation of the corresponding functions.
>
> I like this patch, but how about a slightly different take, make this
> change instead:
>
> -struct tpm_chip *tpm_chip_find_get(int chip_num)
> +struct tpm_chip *tpm_chip_find_get(struct tpm_chip *chip);
>
> Where chip = NULL means the default TPM.
>
> And then at all call sites swap TPM_ANY_NUM to NULL and instead of
> flowing an 'int chip_num' to tpm_chip_find_get, flow the 'struct
> tpm_chip *' directly.
>
> This gets us much closer to the desired API with about the same amount
> of churn as this patch has.
>
> Jason
I can do that. I will rework this as a patch set that includes this
proposal. Gives us more clean position to continue. Thank you.
/Jarkko
WARNING: multiple messages have this Message-ID (diff)
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Cc: linux-integrity@vger.kernel.org,
linux-security-module@vger.kernel.org,
Matt Mackall <mpm@selenic.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Peter Huewe <peterhuewe@gmx.de>,
Marcel Selhorst <tpmdd@selhorst.net>,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
Dmitry Kasatkin <dmitry.kasatkin@gmail.com>,
James Morris <james.l.morris@oracle.com>,
"Serge E. Hallyn" <serge@hallyn.com>,
David Howells <dhowells@redhat.com>,
Jerry Snitselaar <jsnitsel@redhat.com>,
"open list:HARDWARE RANDOM NUMBER GENERATOR CORE"
<linux-crypto@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"open list:KEYS-TRUSTED" <keyrings@vger.kernel.org>
Subject: Re: [PATCH] tpm: remove chip_num parameter from in-kernel API
Date: Wed, 25 Oct 2017 00:27:41 +0200 [thread overview]
Message-ID: <20171024222741.lqvgpdaosjazpvfd@linux.intel.com> (raw)
In-Reply-To: <20171024185208.GD1806@obsidianresearch.com>
On Tue, Oct 24, 2017 at 12:52:08PM -0600, Jason Gunthorpe wrote:
> On Mon, Oct 23, 2017 at 02:38:14PM +0200, Jarkko Sakkinen wrote:
> > The reasoning is simple and obvious. Since every call site passes the
> > value TPM_ANY_NUM (0xFFFF) the parameter does not have right to exist.
> > Refined the documentation of the corresponding functions.
>
> I like this patch, but how about a slightly different take, make this
> change instead:
>
> -struct tpm_chip *tpm_chip_find_get(int chip_num)
> +struct tpm_chip *tpm_chip_find_get(struct tpm_chip *chip);
>
> Where chip == NULL means the default TPM.
>
> And then at all call sites swap TPM_ANY_NUM to NULL and instead of
> flowing an 'int chip_num' to tpm_chip_find_get, flow the 'struct
> tpm_chip *' directly.
>
> This gets us much closer to the desired API with about the same amount
> of churn as this patch has.
>
> Jason
I can do that. I will rework this as a patch set that includes this
proposal. Gives us more clean position to continue. Thank you.
/Jarkko
WARNING: multiple messages have this Message-ID (diff)
From: jarkko.sakkinen@linux.intel.com (Jarkko Sakkinen)
To: linux-security-module@vger.kernel.org
Subject: [PATCH] tpm: remove chip_num parameter from in-kernel API
Date: Wed, 25 Oct 2017 00:27:41 +0200 [thread overview]
Message-ID: <20171024222741.lqvgpdaosjazpvfd@linux.intel.com> (raw)
In-Reply-To: <20171024185208.GD1806@obsidianresearch.com>
On Tue, Oct 24, 2017 at 12:52:08PM -0600, Jason Gunthorpe wrote:
> On Mon, Oct 23, 2017 at 02:38:14PM +0200, Jarkko Sakkinen wrote:
> > The reasoning is simple and obvious. Since every call site passes the
> > value TPM_ANY_NUM (0xFFFF) the parameter does not have right to exist.
> > Refined the documentation of the corresponding functions.
>
> I like this patch, but how about a slightly different take, make this
> change instead:
>
> -struct tpm_chip *tpm_chip_find_get(int chip_num)
> +struct tpm_chip *tpm_chip_find_get(struct tpm_chip *chip);
>
> Where chip == NULL means the default TPM.
>
> And then at all call sites swap TPM_ANY_NUM to NULL and instead of
> flowing an 'int chip_num' to tpm_chip_find_get, flow the 'struct
> tpm_chip *' directly.
>
> This gets us much closer to the desired API with about the same amount
> of churn as this patch has.
>
> Jason
I can do that. I will rework this as a patch set that includes this
proposal. Gives us more clean position to continue. Thank you.
/Jarkko
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-10-24 22:27 UTC|newest]
Thread overview: 123+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-23 12:38 [PATCH] tpm: remove chip_num parameter from in-kernel API Jarkko Sakkinen
2017-10-23 12:38 ` Jarkko Sakkinen
2017-10-23 12:38 ` Jarkko Sakkinen
2017-10-23 12:38 ` Jarkko Sakkinen
2017-10-23 12:38 ` Jarkko Sakkinen
2017-10-23 14:07 ` [tpmdd-devel] " Stefan Berger
2017-10-23 14:07 ` Stefan Berger
2017-10-23 14:07 ` Stefan Berger
2017-10-23 14:07 ` Stefan Berger
2017-10-23 14:07 ` Stefan Berger
2017-10-23 16:31 ` Jason Gunthorpe
2017-10-23 16:31 ` Jason Gunthorpe
2017-10-23 16:31 ` Jason Gunthorpe
2017-10-23 16:31 ` Jason Gunthorpe
2017-10-23 16:31 ` Jason Gunthorpe
2017-10-24 15:44 ` Jarkko Sakkinen
2017-10-24 15:44 ` Jarkko Sakkinen
2017-10-24 15:44 ` Jarkko Sakkinen
2017-10-24 15:44 ` Jarkko Sakkinen
2017-10-24 15:44 ` Jarkko Sakkinen
[not found] ` <20171024154440.3jeupmus43jcgbbz-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-10-24 15:51 ` PrasannaKumar Muralidharan
2017-10-24 15:51 ` [tpmdd-devel] " PrasannaKumar Muralidharan
2017-10-24 15:51 ` PrasannaKumar Muralidharan
2017-10-24 15:51 ` PrasannaKumar Muralidharan
2017-10-24 15:55 ` Jason Gunthorpe
2017-10-24 15:55 ` Jason Gunthorpe
2017-10-24 15:55 ` Jason Gunthorpe
2017-10-24 15:55 ` Jason Gunthorpe
2017-10-24 15:55 ` Jason Gunthorpe
2017-10-24 16:07 ` PrasannaKumar Muralidharan
2017-10-24 16:19 ` PrasannaKumar Muralidharan
2017-10-24 16:07 ` PrasannaKumar Muralidharan
2017-10-24 16:07 ` PrasannaKumar Muralidharan
2017-10-24 16:07 ` PrasannaKumar Muralidharan
2017-10-24 16:11 ` Jason Gunthorpe
2017-10-24 16:11 ` Jason Gunthorpe
2017-10-24 16:11 ` Jason Gunthorpe
2017-10-24 16:11 ` Jason Gunthorpe
2017-10-24 16:11 ` Jason Gunthorpe
2017-10-24 16:14 ` PrasannaKumar Muralidharan
2017-10-24 16:26 ` PrasannaKumar Muralidharan
2017-10-24 16:14 ` PrasannaKumar Muralidharan
2017-10-24 16:14 ` PrasannaKumar Muralidharan
2017-10-24 16:14 ` PrasannaKumar Muralidharan
2017-10-24 17:46 ` Jason Gunthorpe
2017-10-24 17:46 ` Jason Gunthorpe
2017-10-24 17:46 ` Jason Gunthorpe
2017-10-24 17:46 ` Jason Gunthorpe
2017-10-24 17:46 ` Jason Gunthorpe
2017-10-24 17:56 ` PrasannaKumar Muralidharan
2017-10-24 17:56 ` PrasannaKumar Muralidharan
2017-10-24 17:56 ` PrasannaKumar Muralidharan
2017-10-24 17:56 ` PrasannaKumar Muralidharan
2017-10-24 17:56 ` PrasannaKumar Muralidharan
2017-10-24 17:02 ` Dmitry Torokhov
2017-10-24 17:02 ` Dmitry Torokhov
2017-10-24 17:02 ` Dmitry Torokhov
2017-10-24 17:02 ` Dmitry Torokhov
2017-10-24 17:02 ` Dmitry Torokhov
2017-10-24 17:37 ` Jason Gunthorpe
2017-10-24 17:37 ` Jason Gunthorpe
2017-10-24 17:37 ` Jason Gunthorpe
2017-10-24 17:37 ` Jason Gunthorpe
2017-10-24 17:37 ` Jason Gunthorpe
2017-10-24 17:44 ` PrasannaKumar Muralidharan
2017-10-24 17:56 ` PrasannaKumar Muralidharan
2017-10-24 17:44 ` PrasannaKumar Muralidharan
2017-10-24 17:44 ` PrasannaKumar Muralidharan
2017-10-24 17:44 ` PrasannaKumar Muralidharan
[not found] ` <20171024173757.GA1806-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2017-10-24 18:04 ` Dmitry Torokhov
2017-10-24 18:04 ` Dmitry Torokhov
2017-10-24 18:04 ` [tpmdd-devel] " Dmitry Torokhov
2017-10-24 18:04 ` Dmitry Torokhov
2017-10-24 18:04 ` Dmitry Torokhov
2017-10-24 18:15 ` [tpmdd-devel] " Jarkko Sakkinen
2017-10-24 18:15 ` Jarkko Sakkinen
2017-10-24 18:15 ` Jarkko Sakkinen
2017-10-24 18:15 ` Jarkko Sakkinen
2017-10-24 18:15 ` Jarkko Sakkinen
[not found] ` <20171024181512.iaxtzgxexhki7aqr-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-10-24 18:40 ` Peter Huewe
2017-10-24 18:40 ` Peter Huewe
2017-10-24 18:40 ` [tpmdd-devel] " Peter Huewe
2017-10-24 18:40 ` Peter Huewe
2017-10-24 18:40 ` Peter Huewe
2017-10-24 16:23 ` [tpmdd-devel] " Jarkko Sakkinen
2017-10-24 16:23 ` Jarkko Sakkinen
2017-10-24 16:23 ` Jarkko Sakkinen
2017-10-24 16:23 ` Jarkko Sakkinen
2017-10-24 16:23 ` Jarkko Sakkinen
2017-10-24 16:35 ` PrasannaKumar Muralidharan
2017-10-24 16:47 ` PrasannaKumar Muralidharan
2017-10-24 16:35 ` PrasannaKumar Muralidharan
2017-10-24 16:35 ` PrasannaKumar Muralidharan
2017-10-24 16:35 ` PrasannaKumar Muralidharan
[not found] ` <CANc+2y4vtr+kbhC_7Rv=rHA2LgEVBHLFEu+DYYK1UmpU63PCgQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-10-24 18:22 ` Jarkko Sakkinen
2017-10-24 18:22 ` Jarkko Sakkinen
2017-10-24 18:22 ` Jarkko Sakkinen
2017-10-24 18:22 ` Jarkko Sakkinen
[not found] ` <20171024182235.d7b3oajc5zcjs57v-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-10-25 14:51 ` PrasannaKumar Muralidharan
2017-10-25 14:51 ` [tpmdd-devel] " PrasannaKumar Muralidharan
2017-10-25 14:51 ` PrasannaKumar Muralidharan
2017-10-25 14:51 ` PrasannaKumar Muralidharan
2017-10-25 19:11 ` Jarkko Sakkinen
2017-10-25 19:11 ` Jarkko Sakkinen
2017-10-25 19:11 ` Jarkko Sakkinen
2017-10-25 19:11 ` Jarkko Sakkinen
2017-10-25 19:11 ` Jarkko Sakkinen
2017-10-26 16:23 ` PrasannaKumar Muralidharan
2017-10-26 16:35 ` PrasannaKumar Muralidharan
2017-10-26 16:23 ` PrasannaKumar Muralidharan
2017-10-26 16:23 ` PrasannaKumar Muralidharan
2017-10-26 16:23 ` PrasannaKumar Muralidharan
2017-10-24 14:04 ` Jarkko Sakkinen
2017-10-24 14:04 ` Jarkko Sakkinen
2017-10-24 14:04 ` Jarkko Sakkinen
2017-10-24 14:04 ` Jarkko Sakkinen
2017-10-24 14:04 ` Jarkko Sakkinen
2017-10-24 18:52 ` Jason Gunthorpe
2017-10-24 18:52 ` Jason Gunthorpe
2017-10-24 18:52 ` Jason Gunthorpe
2017-10-24 22:27 ` Jarkko Sakkinen [this message]
2017-10-24 22:27 ` Jarkko Sakkinen
2017-10-24 22:27 ` 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=20171024222741.lqvgpdaosjazpvfd@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=dhowells@redhat.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=james.l.morris@oracle.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=jsnitsel@redhat.com \
--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=mpm@selenic.com \
--cc=peterhuewe@gmx.de \
--cc=serge@hallyn.com \
--cc=tpmdd@selhorst.net \
--cc=zohar@linux.vnet.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 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.