mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Kent Yoder <key@linux.vnet.ibm.com>
Cc: Kent Yoder <shpedoikal@gmail.com>,
	James Morris <jmorris@namei.org>,
	linux-kernel@vger.kernel.org,
	linux-security-module@vger.kernel.org,
	tpmdd-devel@lists.sourceforge.net,
	Peter Huewe <peter.huewe@infineon.com>,
	Bryan Freed <bfreed@chromium.org>,
	David Safford <safford@linux.vnet.ibm.com>
Subject: Re: [GIT PULL] New TPM driver, hwrng driver and fixes
Date: Mon, 30 Jul 2012 13:52:57 -0700	[thread overview]
Message-ID: <5016F429.9030800@zytor.com> (raw)
In-Reply-To: <20120730205116.GA22156@linux.vnet.ibm.com>

On 07/30/2012 01:51 PM, Kent Yoder wrote:
> 
>>> Perhaps we should just do the same "err = total ? total : -EIO;" here
>>> and the above statement can just turn into a break;.
>>
>>   Yeah, this seems like the right thing to do.
>>
>>>> -     ret = my_get_random(hash, SHA1_DIGEST_SIZE);
>>>> +     ret = tpm_get_random(TPM_ANY_NUM, hash, SHA1_DIGEST_SIZE);
>>>>       if (ret < 0)
>>>>               return ret;
>>>
>>> You are still not checking the return values correctly!
>>
>>   Dave, can you weigh in on these individual cases?  In some cases
>> like capping a pcr I think using uninitialized stack data could be
>> better than failing...
> 
> I got in touch with Dave today, who'd like the full checking done now
> that we can. Here's a new patch, let me know what you think...
> 
> Thanks,
> Kent
> 

Looks good to me.

Reviewed-by: H. Peter Anvin <hpa@linux.intel.com>

	-hpa


  reply	other threads:[~2012-07-30 20:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-27 18:14 Kent Yoder
2012-07-27 18:24 ` H. Peter Anvin
2012-07-27 19:36   ` Kent Yoder
2012-07-27 20:30   ` Kent Yoder
2012-07-27 22:09     ` H. Peter Anvin
2012-07-28  0:45       ` Kent Yoder
2012-07-30 20:51         ` Kent Yoder
2012-07-30 20:52           ` H. Peter Anvin [this message]
2012-08-13 20:44 ` H. Peter Anvin
2012-08-14 16:37   ` Kent Yoder

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=5016F429.9030800@zytor.com \
    --to=hpa@zytor.com \
    --cc=bfreed@chromium.org \
    --cc=jmorris@namei.org \
    --cc=key@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=peter.huewe@infineon.com \
    --cc=safford@linux.vnet.ibm.com \
    --cc=shpedoikal@gmail.com \
    --cc=tpmdd-devel@lists.sourceforge.net \
    /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

Powered by JetHome