All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: PrasannaKumar Muralidharan <prasannatsmkumar@gmail.com>
Cc: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
	Stefan Berger <stefanb@linux.vnet.ibm.com>,
	linux-integrity@vger.kernel.org,
	David Howells <dhowells@redhat.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Dmitry Kasatkin <dmitry.kasatkin@gmail.com>,
	open list <linux-kernel@vger.kernel.org>,
	"open list:INTEGRITY MEASUREMENT ARCHITECTURE (IMA)"
	<linux-security-module@vger.kernel.org>,
	"open list:KEYS-TRUSTED" <keyrings@vger.kernel.org>,
	"open list:HARDWARE RANDOM NUMBER GENERATOR CORE"
	<linux-crypto@vger.kernel.org>,
	James Morris <james.l.morris@oracle.com>,
	Matt Mackall <mpm@selenic.com>,
	David Safford <safford@us.ibm.com>,
	Mimi Zohar <zohar@linux.vnet.ibm.com>,
	"Serge E. Hallyn" <serge@hallyn.com>
Subject: Re: [PATCH v2] tpm: Move Linux RNG connection to hwrng
Date: Tue, 07 Nov 2017 16:04:04 +0000	[thread overview]
Message-ID: <20171107160404.GG21466@ziepe.ca> (raw)
In-Reply-To: <CANc+2y6dx_2zOzFA5aFs7RpEV8aNqxpDghmx+q_+XyendYJoew@mail.gmail.com>

On Tue, Nov 07, 2017 at 08:50:44AM +0530, PrasannaKumar Muralidharan wrote:

> I am assuming you are talking about the following patches - using
> struct tpm_chip instead of chip number and this patch.

yes

> I won't be able to test if struct tpm_chip usage as I don't have
> multiple tpm hw in one machine. In case of tpm rng changes I can test
> only the lifecycle of tpm rng device. Is that enough? I feel my test
> will be limited. Please provide your thoughts on this.

That is certainly better than no testing.

Jason

WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@ziepe.ca>
To: PrasannaKumar Muralidharan <prasannatsmkumar@gmail.com>
Cc: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
	Stefan Berger <stefanb@linux.vnet.ibm.com>,
	linux-integrity@vger.kernel.org,
	David Howells <dhowells@redhat.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Dmitry Kasatkin <dmitry.kasatkin@gmail.com>,
	open list <linux-kernel@vger.kernel.org>,
	"open list:INTEGRITY MEASUREMENT ARCHITECTURE (IMA)"
	<linux-security-module@vger.kernel.org>,
	"open list:KEYS-TRUSTED" <keyrings@vger.kernel.org>,
	"open list:HARDWARE RANDOM NUMBER GENERATOR CORE"
	<linux-crypto@vger.kernel.org>,
	James Morris <james.l.morris@oracle.com>,
	Matt Mackall <mpm@selenic.com>,
	David Safford <safford@us.ibm.com>,
	Mimi Zohar <zohar@linux.vnet.ibm.com>,
	"Serge E. Hallyn" <serge@hallyn.com>
Subject: Re: [PATCH v2] tpm: Move Linux RNG connection to hwrng
Date: Tue, 7 Nov 2017 09:04:04 -0700	[thread overview]
Message-ID: <20171107160404.GG21466@ziepe.ca> (raw)
In-Reply-To: <CANc+2y6dx_2zOzFA5aFs7RpEV8aNqxpDghmx+q_+XyendYJoew@mail.gmail.com>

On Tue, Nov 07, 2017 at 08:50:44AM +0530, PrasannaKumar Muralidharan wrote:

> I am assuming you are talking about the following patches - using
> struct tpm_chip instead of chip number and this patch.

yes

> I won't be able to test if struct tpm_chip usage as I don't have
> multiple tpm hw in one machine. In case of tpm rng changes I can test
> only the lifecycle of tpm rng device. Is that enough? I feel my test
> will be limited. Please provide your thoughts on this.

That is certainly better than no testing.

Jason

WARNING: multiple messages have this Message-ID (diff)
From: jgg@ziepe.ca (Jason Gunthorpe)
To: linux-security-module@vger.kernel.org
Subject: [PATCH v2] tpm: Move Linux RNG connection to hwrng
Date: Tue, 7 Nov 2017 09:04:04 -0700	[thread overview]
Message-ID: <20171107160404.GG21466@ziepe.ca> (raw)
In-Reply-To: <CANc+2y6dx_2zOzFA5aFs7RpEV8aNqxpDghmx+q_+XyendYJoew@mail.gmail.com>

On Tue, Nov 07, 2017 at 08:50:44AM +0530, PrasannaKumar Muralidharan wrote:

> I am assuming you are talking about the following patches - using
> struct tpm_chip instead of chip number and this patch.

yes

> I won't be able to test if struct tpm_chip usage as I don't have
> multiple tpm hw in one machine. In case of tpm rng changes I can test
> only the lifecycle of tpm rng device. Is that enough? I feel my test
> will be limited. Please provide your thoughts on this.

That is certainly better than no testing.

Jason
--
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

  reply	other threads:[~2017-11-07 16:04 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-31 20:05 [PATCH v2] tpm: Move Linux RNG connection to hwrng Jason Gunthorpe
2017-10-31 20:05 ` Jason Gunthorpe
2017-10-31 20:05 ` Jason Gunthorpe
2017-10-31 20:05 ` Jason Gunthorpe
2017-11-05 11:05 ` Jarkko Sakkinen
2017-11-05 11:05   ` Jarkko Sakkinen
2017-11-05 11:05   ` Jarkko Sakkinen
2017-11-05 11:05   ` Jarkko Sakkinen
2017-11-06  2:27   ` Jason Gunthorpe
2017-11-06  2:27     ` Jason Gunthorpe
2017-11-06  2:27     ` Jason Gunthorpe
2017-11-07  3:20     ` PrasannaKumar Muralidharan
2017-11-07  3:32       ` PrasannaKumar Muralidharan
2017-11-07  3:20       ` PrasannaKumar Muralidharan
2017-11-07 16:04       ` Jason Gunthorpe [this message]
2017-11-07 16:04         ` Jason Gunthorpe
2017-11-07 16:04         ` Jason Gunthorpe
2017-11-09 16:19         ` PrasannaKumar Muralidharan
2017-11-09 16:31           ` PrasannaKumar Muralidharan
2017-11-09 16:19           ` PrasannaKumar Muralidharan
2017-11-09 16:29           ` Jason Gunthorpe
2017-11-09 16:29             ` Jason Gunthorpe
2017-11-09 16:29             ` Jason Gunthorpe
2017-11-12  5:27             ` PrasannaKumar Muralidharan
2017-11-12  5:39               ` PrasannaKumar Muralidharan
2017-11-12  5:27               ` PrasannaKumar Muralidharan
2017-11-14 14:34         ` Jarkko Sakkinen
2017-11-14 14:34           ` Jarkko Sakkinen
2017-11-14 14:34           ` Jarkko Sakkinen
2017-11-17 13:28           ` Jarkko Sakkinen
2017-11-17 13:28             ` Jarkko Sakkinen
2017-11-17 13:28             ` Jarkko Sakkinen
2017-11-17 13:57             ` Jarkko Sakkinen
2017-11-17 13:57               ` Jarkko Sakkinen
2017-11-17 13:57               ` Jarkko Sakkinen
2018-01-27  6:50               ` PrasannaKumar Muralidharan
2018-01-27  6:50                 ` PrasannaKumar Muralidharan
2018-01-27  6:50                 ` PrasannaKumar Muralidharan
2018-01-29 22:06                 ` Jarkko Sakkinen
2018-01-29 22:06                   ` Jarkko Sakkinen
2018-01-29 22:06                   ` Jarkko Sakkinen
2018-01-30 11:52                   ` James Morris
2018-01-30 11:52                     ` James Morris
2018-01-30 11:52                     ` James Morris
2018-01-30 15:28                     ` Jarkko Sakkinen
2018-01-30 15:28                       ` Jarkko Sakkinen
2018-01-30 15:28                       ` Jarkko Sakkinen
2017-11-07 19:24     ` Jarkko Sakkinen
2017-11-07 19:24       ` Jarkko Sakkinen
2017-11-07 19:24       ` 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=20171107160404.GG21466@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=dhowells@redhat.com \
    --cc=dmitry.kasatkin@gmail.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=james.l.morris@oracle.com \
    --cc=jarkko.sakkinen@linux.intel.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=prasannatsmkumar@gmail.com \
    --cc=safford@us.ibm.com \
    --cc=serge@hallyn.com \
    --cc=stefanb@linux.vnet.ibm.com \
    --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.