stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Matthew Garrett <matthewgarrett@google.com>
Cc: linux-integrity@vger.kernel.org,
	Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
	Matthew Garrett <mjg59@google.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH] tpm: Don't make log failures fatal
Date: Tue, 17 Dec 2019 13:15:14 +0100	[thread overview]
Message-ID: <3a472005-83a7-9787-0bfc-35673702be09@molgen.mpg.de> (raw)
In-Reply-To: <20191213225748.11256-1-matthewgarrett@google.com>

Dear Matthew,


Am 13.12.19 um 23:57 schrieb Matthew Garrett:
> If a TPM is in disabled state, it's reasonable for it to have an empty
> log. Bailing out of probe in this case means that the PPI interface
> isn't available, so there's no way to then enable the TPM from the OS.
> In general it seems reasonable to ignore log errors - they shouldn't
> itnerfere with any other TPM functionality.

interfere

Can this be tested with QEMU somehow?

> Signed-off-by: Matthew Garrett <mjg59@google.com>
> Cc: stable@vger.kernel.org
> ---
>   drivers/char/tpm/tpm-chip.c | 4 +---
>   1 file changed, 1 insertion(+), 3 deletions(-)
> 
> diff --git a/drivers/char/tpm/tpm-chip.c b/drivers/char/tpm/tpm-chip.c
> index 3d6d394a8661..58073836b555 100644
> --- a/drivers/char/tpm/tpm-chip.c
> +++ b/drivers/char/tpm/tpm-chip.c
> @@ -596,9 +596,7 @@ int tpm_chip_register(struct tpm_chip *chip)
>   
>   	tpm_sysfs_add_device(chip);
>   
> -	rc = tpm_bios_log_setup(chip);
> -	if (rc != 0 && rc != -ENODEV)
> -		return rc;
> +	tpm_bios_log_setup(chip);
>   
>   	tpm_add_ppi(chip);

Acked-by: Paul Menzel <pmenzel@molgen.mpg.de>


Kind regards,

Paul

  parent reply	other threads:[~2019-12-17 12:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-13 22:57 [PATCH] tpm: Don't make log failures fatal Matthew Garrett
2019-12-17 10:54 ` Jarkko Sakkinen
2019-12-17 12:15 ` Paul Menzel [this message]
2020-01-02 22:11   ` Matthew Garrett

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=3a472005-83a7-9787-0bfc-35673702be09@molgen.mpg.de \
    --to=pmenzel@molgen.mpg.de \
    --cc=jarkko.sakkinen@linux.intel.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=matthewgarrett@google.com \
    --cc=mjg59@google.com \
    --cc=stable@vger.kernel.org \
    /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).