From: Paul Bolle <pebolle@tiscali.nl>
To: Rajiv Andrade <srajiv@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, tpmdd-devel@lists.sourceforge.net
Subject: Re: [PATCH] TPM: chip disabled state erronously being reported as error
Date: Wed, 25 Apr 2012 11:41:50 +0200 [thread overview]
Message-ID: <1335346910.1611.9.camel@t41.thuisdomein> (raw)
In-Reply-To: <20120424205717.GA3755@localhost>
Rajiv,
On Tue, 2012-04-24 at 17:57 -0300, Rajiv Andrade wrote:
> Can you test it?
Sure. Your patch applied cleanly to the current Fedora 16 kernel's
sources (ie, kernel-3.3.2-6.fc16). One boot and one suspend-and-resume
cycle both were without the error message that bothered me so much.
That should be all testing that this patch needs, shouldn't it?
> tpm_do_selftest() attempts to read a PCR in order to
> decide if one can rely on the TPM being used or not.
> The function that's used by __tpm_pcr_read() does not
> expect the TPM to be disabled or deactivated, and if so,
> reports an error.
>
> It's fine if the TPM returns this error when trying to
> use it for the first time after a power cycle, but it's
> definitely not if it already returned success for a
> previous attempt to read one of its PCRs.
>
> The tpm_do_selftest() was modified so that the driver only
> reports this return code as an error when it really is.
>
> Reported-by: Paul Bolle <pebolle@tiscali.nl>
I guess that is now "Reported-and-tested-by", even though the test was
run against a v3.3.2 based kernel.
> Signed-off-by: Rajiv Andrade <srajiv@linux.vnet.ibm.com>
Should this be CC-ed to stable for v3.3?
Paul Bolle
prev parent reply other threads:[~2012-04-25 9:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 20:57 Rajiv Andrade
2012-04-25 9:41 ` Paul Bolle [this message]
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=1335346910.1611.9.camel@t41.thuisdomein \
--to=pebolle@tiscali.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=srajiv@linux.vnet.ibm.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
all inboxes | Powered by JetHome®