From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: linux-integrity@vger.kernel.org, Mimi Zohar <zohar@linux.ibm.com>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Sumit Garg <sumit.garg@linaro.org>,
Stefan Berger <stefanb@linux.vnet.ibm.com>,
Peter Huewe <peterhuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] tpm: Detach page allocation from tpm_buf
Date: Tue, 1 Oct 2019 23:51:50 +0300 [thread overview]
Message-ID: <20191001205150.GA26709@linux.intel.com> (raw)
In-Reply-To: <20190928075813.nsmu3g7derj2fjmj@cantor>
On Sat, Sep 28, 2019 at 12:58:13AM -0700, Jerry Snitselaar wrote:
> TPM2_CC_GET_RANDOM
Ugh, I somehow sent v1 2nd time also in terms of contents (was fixed in
v2).
I think it would be a great idea to add call to tpm_get_random() to the
chip startup as an additional test.
> Would this work here?
>
> err = total ? total : -EIO;
> out:
> kunmap(data_page);
> __free_page(data_page);
> return err;
I'd guess but I want to keep this commit as dumbed down and mechanical
as possible given the amount of changes.
/Jarkko
next prev parent reply other threads:[~2019-10-01 20:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 17:23 [PATCH] tpm: Detach page allocation from tpm_buf Jarkko Sakkinen
2019-09-27 15:42 ` Jarkko Sakkinen
2019-09-28 7:58 ` Jerry Snitselaar
2019-10-01 20:51 ` Jarkko Sakkinen [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-09-25 13:48 Jarkko Sakkinen
2019-09-25 14:03 ` James Bottomley
2019-09-27 13:06 ` Jarkko Sakkinen
2019-10-02 12:41 ` Mimi Zohar
2019-10-03 11:35 ` Jarkko Sakkinen
2019-10-03 12:50 ` Mimi Zohar
2019-10-03 18:26 ` Jarkko Sakkinen
2019-09-26 12:46 ` Jarkko Sakkinen
2019-09-26 13:12 ` Jarkko Sakkinen
2019-10-02 12:40 ` Mimi Zohar
2019-10-03 11:32 ` Jarkko Sakkinen
2019-10-03 11:33 ` Jarkko Sakkinen
2019-10-03 15:24 ` Mimi Zohar
2019-10-03 18:33 ` Jarkko Sakkinen
2019-10-03 12:39 ` Mimi Zohar
2019-10-03 18:31 ` 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=20191001205150.GA26709@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterhuewe@gmx.de \
--cc=stefanb@linux.vnet.ibm.com \
--cc=sumit.garg@linaro.org \
--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).