linux-integrity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Javier Martinez Canillas <javierm@redhat.com>
Cc: linux-kernel@vger.kernel.org, Hans de Goede <hdegoede@redhat.com>,
	Arnd Bergmann <arnd@arndb.de>, Peter Huewe <peterhuewe@gmx.de>,
	Jason Gunthorpe <jgg@ziepe.ca>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-integrity@vger.kernel.org
Subject: Re: [PATCH] tpm: suppress transmit cmd error logs when TPM 1.2 is disabled/deactivated
Date: Wed, 5 Sep 2018 14:14:27 +0300	[thread overview]
Message-ID: <20180905111427.GB9696@linux.intel.com> (raw)
In-Reply-To: <20180830144005.6768-1-javierm@redhat.com>

On Thu, Aug 30, 2018 at 04:40:05PM +0200, Javier Martinez Canillas wrote:
> For TPM 1.2 chips the system setup utility allows to set the TPM device in
> one of the following states:
> 
>   * Active: Security chip is functional
>   * Inactive: Security chip is visible, but is not functional
>   * Disabled: Security chip is hidden and is not functional
> 
> When choosing the "Inactive" state, the TPM 1.2 device is enumerated and
> registered, but sending TPM commands fail with either TPM_DEACTIVATED or
> TPM_DISABLED depending if the firmware deactivated or disabled the TPM.
> 
> Since these TPM 1.2 error codes don't have special treatment, inactivating
> the TPM leads to a very noisy kernel log buffer that shows messages like
> the following:
> 
>   tpm_tis 00:05: 1.2 TPM (device-id 0x0, rev-id 78)
>   tpm tpm0: A TPM error (6) occurred attempting to read a pcr value
>   tpm tpm0: TPM is disabled/deactivated (0x6)
>   tpm tpm0: A TPM error (6) occurred attempting get random
>   tpm tpm0: A TPM error (6) occurred attempting to read a pcr value
>   ima: No TPM chip found, activating TPM-bypass! (rc=6)
>   tpm tpm0: A TPM error (6) occurred attempting get random
>   tpm tpm0: A TPM error (6) occurred attempting get random
>   tpm tpm0: A TPM error (6) occurred attempting get random
>   tpm tpm0: A TPM error (6) occurred attempting get random
> 
> Let's just suppress error log messages for the TPM_{DEACTIVATED,DISABLED}
> return codes, since this is expected when the TPM 1.2 is set to Inactive.
> 
> In that case the kernel log is cleaner and less confusing for users, i.e:
> 
>   tpm_tis 00:05: 1.2 TPM (device-id 0x0, rev-id 78)
>   tpm tpm0: TPM is disabled/deactivated (0x6)
>   ima: No TPM chip found, activating TPM-bypass! (rc=6)
> 
> Reported-by: Hans de Goede <hdegoede@redhat.com>
> Signed-off-by: Javier Martinez Canillas <javierm@redhat.com>
> 
> ---
> 
>  drivers/char/tpm/tpm-interface.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/char/tpm/tpm-interface.c b/drivers/char/tpm/tpm-interface.c
> index 1a803b0cf98..9f61106502a 100644
> --- a/drivers/char/tpm/tpm-interface.c
> +++ b/drivers/char/tpm/tpm-interface.c
> @@ -663,7 +663,8 @@ ssize_t tpm_transmit_cmd(struct tpm_chip *chip, struct tpm_space *space,
>  		return len;
>  
>  	err = be32_to_cpu(header->return_code);
> -	if (err != 0 && desc)
> +	if (err != 0 && err != TPM_ERR_DISABLED && err != TPM_ERR_DEACTIVATED
> +	    && desc)
>  		dev_err(&chip->dev, "A TPM error (%d) occurred %s\n", err,
>  			desc);
>  	if (err)
> -- 
> 2.17.1
> 

Reviewed-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>

/Jarkko

      reply	other threads:[~2018-09-05 15:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-30 14:40 [PATCH] tpm: suppress transmit cmd error logs when TPM 1.2 is disabled/deactivated Javier Martinez Canillas
2018-09-05 11:14 ` Jarkko Sakkinen [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=20180905111427.GB9696@linux.intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=hdegoede@redhat.com \
    --cc=javierm@redhat.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterhuewe@gmx.de \
    /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).