All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Matthew Garrett <matthewgarrett@google.com>,
	linux-integrity@vger.kernel.org
Cc: Matthew Garrett <mjg59@google.com>, stable@vger.kernel.org
Subject: Re: [PATCH] tpm: Don't make log failures fatal
Date: Tue, 17 Dec 2019 12:54:35 +0200	[thread overview]
Message-ID: <71bb3bdebe302fcc8254ba9e8b607001bb87aa1b.camel@linux.intel.com> (raw)
In-Reply-To: <20191213225748.11256-1-matthewgarrett@google.com>

On Fri, 2019-12-13 at 14:57 -0800, Matthew Garrett wrote:
> 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.
> 
> Signed-off-by: Matthew Garrett <mjg59@google.com>
> Cc: stable@vger.kernel.org

Otherwise looks great but maybe it would make sense to change
tpm_bios_log_setup() as void as part of the change?

> ---
>  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);
>  

/Jarkko


  reply	other threads:[~2019-12-17 10:54 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 [this message]
2019-12-17 12:15 ` Paul Menzel
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=71bb3bdebe302fcc8254ba9e8b607001bb87aa1b.camel@linux.intel.com \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.