From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Cc: PrasannaKumar Muralidharan <prasannatsmkumar@gmail.com>,
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 Safford <safford@us.ibm.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>,
"moderated list:TPM DEVICE DRIVER"
<tpmdd-devel@lists.sourceforge.net>
Subject: Re: [PATCH v2] tpm: use struct tpm_chip for tpm_chip_find_get()
Date: Thu, 26 Oct 2017 10:54:30 +0000 [thread overview]
Message-ID: <20171026105430.t6khk6cekk3cyfrs@linux.intel.com> (raw)
In-Reply-To: <20171025201744.GB2815@obsidianresearch.com>
On Wed, Oct 25, 2017 at 02:17:44PM -0600, Jason Gunthorpe wrote:
> On Wed, Oct 25, 2017 at 10:07:46PM +0200, Jarkko Sakkinen wrote:
>
> > The id has a nice feature that it is unique for one boot cycle you can
> > even try to get a chip that has been deleted. It has the most stable
> > properties in the long run.
>
> It isn't unique, we can re-use ids them via idr_alloc(). We should
> never use index inside the kernel.
>
> > Address is a reusable identifier in one boot cycle.
>
> It is invalid to pass in a chip for which the caller does not hold a
> kref, so address is the safest argument.
>
> Jason
I'll buy this too (sending update today).
/Jarkko
WARNING: multiple messages have this Message-ID (diff)
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Cc: PrasannaKumar Muralidharan <prasannatsmkumar@gmail.com>,
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 Safford <safford@us.ibm.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>,
"moderated list:TPM DEVICE DRIVER"
<tpmdd-devel@lists.sourceforge.net>,
Subject: Re: [PATCH v2] tpm: use struct tpm_chip for tpm_chip_find_get()
Date: Thu, 26 Oct 2017 12:54:30 +0200 [thread overview]
Message-ID: <20171026105430.t6khk6cekk3cyfrs@linux.intel.com> (raw)
In-Reply-To: <20171025201744.GB2815@obsidianresearch.com>
On Wed, Oct 25, 2017 at 02:17:44PM -0600, Jason Gunthorpe wrote:
> On Wed, Oct 25, 2017 at 10:07:46PM +0200, Jarkko Sakkinen wrote:
>
> > The id has a nice feature that it is unique for one boot cycle you can
> > even try to get a chip that has been deleted. It has the most stable
> > properties in the long run.
>
> It isn't unique, we can re-use ids them via idr_alloc(). We should
> never use index inside the kernel.
>
> > Address is a reusable identifier in one boot cycle.
>
> It is invalid to pass in a chip for which the caller does not hold a
> kref, so address is the safest argument.
>
> Jason
I'll buy this too (sending update today).
/Jarkko
WARNING: multiple messages have this Message-ID (diff)
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Cc: PrasannaKumar Muralidharan <prasannatsmkumar@gmail.com>,
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 Safford <safford@us.ibm.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>,
"moderated list:TPM DEVICE DRIVER"
<tpmdd-devel@lists.sourceforge.net>,
"open list:INTEGRITY MEASUREMENT ARCHITECTURE (IMA)"
<linux-ima-devel@lists.sourceforge.net>,
"open list:INTEGRITY MEASUREMENT ARCHITECTURE (IMA)"
<linux-ima-user@lists.sourceforge.net>,
"open list:KEYS-TRUSTED" <keyrings@vger.kernel.org>
Subject: Re: [PATCH v2] tpm: use struct tpm_chip for tpm_chip_find_get()
Date: Thu, 26 Oct 2017 12:54:30 +0200 [thread overview]
Message-ID: <20171026105430.t6khk6cekk3cyfrs@linux.intel.com> (raw)
In-Reply-To: <20171025201744.GB2815@obsidianresearch.com>
On Wed, Oct 25, 2017 at 02:17:44PM -0600, Jason Gunthorpe wrote:
> On Wed, Oct 25, 2017 at 10:07:46PM +0200, Jarkko Sakkinen wrote:
>
> > The id has a nice feature that it is unique for one boot cycle you can
> > even try to get a chip that has been deleted. It has the most stable
> > properties in the long run.
>
> It isn't unique, we can re-use ids them via idr_alloc(). We should
> never use index inside the kernel.
>
> > Address is a reusable identifier in one boot cycle.
>
> It is invalid to pass in a chip for which the caller does not hold a
> kref, so address is the safest argument.
>
> Jason
I'll buy this too (sending update today).
/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 v2] tpm: use struct tpm_chip for tpm_chip_find_get()
Date: Thu, 26 Oct 2017 12:54:30 +0200 [thread overview]
Message-ID: <20171026105430.t6khk6cekk3cyfrs@linux.intel.com> (raw)
In-Reply-To: <20171025201744.GB2815@obsidianresearch.com>
On Wed, Oct 25, 2017 at 02:17:44PM -0600, Jason Gunthorpe wrote:
> On Wed, Oct 25, 2017 at 10:07:46PM +0200, Jarkko Sakkinen wrote:
>
> > The id has a nice feature that it is unique for one boot cycle you can
> > even try to get a chip that has been deleted. It has the most stable
> > properties in the long run.
>
> It isn't unique, we can re-use ids them via idr_alloc(). We should
> never use index inside the kernel.
>
> > Address is a reusable identifier in one boot cycle.
>
> It is invalid to pass in a chip for which the caller does not hold a
> kref, so address is the safest argument.
>
> Jason
I'll buy this too (sending update today).
/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
WARNING: multiple messages have this Message-ID (diff)
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Cc: PrasannaKumar Muralidharan <prasannatsmkumar@gmail.com>,
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 Safford <safford@us.ibm.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>,
"moderated list:TPM DEVICE DRIVER"
<tpmdd-devel@lists.sourceforge.net>
Subject: Re: [PATCH v2] tpm: use struct tpm_chip for tpm_chip_find_get()
Date: Thu, 26 Oct 2017 12:54:30 +0200 [thread overview]
Message-ID: <20171026105430.t6khk6cekk3cyfrs@linux.intel.com> (raw)
In-Reply-To: <20171025201744.GB2815@obsidianresearch.com>
On Wed, Oct 25, 2017 at 02:17:44PM -0600, Jason Gunthorpe wrote:
> On Wed, Oct 25, 2017 at 10:07:46PM +0200, Jarkko Sakkinen wrote:
>
> > The id has a nice feature that it is unique for one boot cycle you can
> > even try to get a chip that has been deleted. It has the most stable
> > properties in the long run.
>
> It isn't unique, we can re-use ids them via idr_alloc(). We should
> never use index inside the kernel.
>
> > Address is a reusable identifier in one boot cycle.
>
> It is invalid to pass in a chip for which the caller does not hold a
> kref, so address is the safest argument.
>
> Jason
I'll buy this too (sending update today).
/Jarkko
next prev parent reply other threads:[~2017-10-26 10:54 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 11:55 [PATCH v2] tpm: use struct tpm_chip for tpm_chip_find_get() Jarkko Sakkinen
2017-10-25 11:55 ` Jarkko Sakkinen
2017-10-25 11:55 ` Jarkko Sakkinen
2017-10-25 11:55 ` Jarkko Sakkinen
2017-10-25 11:55 ` Jarkko Sakkinen
2017-10-25 15:10 ` PrasannaKumar Muralidharan
2017-10-25 15:22 ` PrasannaKumar Muralidharan
2017-10-25 15:10 ` PrasannaKumar Muralidharan
2017-10-25 15:10 ` PrasannaKumar Muralidharan
2017-10-25 15:10 ` PrasannaKumar Muralidharan
2017-10-25 19:34 ` Jarkko Sakkinen
2017-10-25 19:34 ` Jarkko Sakkinen
2017-10-25 19:34 ` Jarkko Sakkinen
2017-10-25 19:34 ` Jarkko Sakkinen
2017-10-25 19:34 ` Jarkko Sakkinen
2017-10-25 19:46 ` Jason Gunthorpe
2017-10-25 19:46 ` Jason Gunthorpe
2017-10-25 19:46 ` Jason Gunthorpe
2017-10-25 19:46 ` Jason Gunthorpe
2017-10-25 19:46 ` Jason Gunthorpe
2017-10-25 20:07 ` Jarkko Sakkinen
2017-10-25 20:07 ` Jarkko Sakkinen
2017-10-25 20:07 ` Jarkko Sakkinen
2017-10-25 20:07 ` Jarkko Sakkinen
2017-10-25 20:07 ` Jarkko Sakkinen
[not found] ` <20171025200746.svsraubdotjyzt2i-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-10-25 20:17 ` Jason Gunthorpe
2017-10-25 20:17 ` Jason Gunthorpe
2017-10-25 20:17 ` Jason Gunthorpe
2017-10-25 20:17 ` Jason Gunthorpe
2017-10-25 20:17 ` Jason Gunthorpe
2017-10-26 10:54 ` Jarkko Sakkinen [this message]
2017-10-26 10:54 ` Jarkko Sakkinen
2017-10-26 10:54 ` Jarkko Sakkinen
2017-10-26 10:54 ` Jarkko Sakkinen
2017-10-26 10:54 ` Jarkko Sakkinen
2017-10-25 15:22 ` Jason Gunthorpe
2017-10-25 15:22 ` Jason Gunthorpe
2017-10-25 15:22 ` Jason Gunthorpe
2017-10-25 15:22 ` Jason Gunthorpe
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=20171026105430.t6khk6cekk3cyfrs@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=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=prasannatsmkumar@gmail.com \
--cc=safford@us.ibm.com \
--cc=serge@hallyn.com \
--cc=tpmdd-devel@lists.sourceforge.net \
--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.