All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Mahnke-Hartmann <stefan.mahnke-hartmann@infineon.com>
To: <martenli@axis.com>
Cc: <Marten.Lindahl@axis.com>, <jarkko@kernel.org>, <jgg@ziepe.ca>,
	<kernel@axis.com>, <linux-integrity@vger.kernel.org>,
	<peterhuewe@gmx.de>
Subject: Re: [PATCH] tpm: Add check for Failure mode for TPM2 modules
Date: Fri, 6 May 2022 14:00:41 +0200	[thread overview]
Message-ID: <20220506120041.228769-1-stefan.mahnke-hartmann@infineon.com> (raw)
In-Reply-To: <YmbDpMUtUK/NrXIY@axis.com>

> On Mon, Apr 25, 2022 at 04:03:33PM +0200, Jarkko Sakkinen wrote:
> > On Mon, 2022-04-25 at 12:25 +0200, Mårten Lindahl wrote:
> > > In commit 0aa698787aa2 ("tpm: Add Upgrade/Reduced mode support for
> > > TPM2 modules") it was said that:
> > > 
> > > "If the TPM is in Failure mode, it will successfully respond to both
> > > tpm2_do_selftest() and tpm2_startup() calls. Although, will fail to
> > > answer to tpm2_get_cc_attrs_tbl(). Use this fact to conclude that TPM
> > > is in Failure mode."
> > > 
> > > But a check was never added in the commit when calling
> > > tpm2_get_cc_attrs_tbl() to conclude that the TPM is in Failure mode.
> > > This commit corrects this by adding a check.
> > > 
> > > Signed-off-by: Mårten Lindahl <marten.lindahl@axis.com>
> > 
> > Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
> > 
> > I think this should actually have the fixes tag. It's a regression,
> > right? I can add it.
>
> Hi Jarkko!
>
> Thank you. Yes it should have a fixes tag for the mentioned commit.
>
> Kind regards
> Mårten
>
> > 
> > BR, Jarkko

Hi Mårten,

your patch introduces redundant code. The code block of the if below
contains exactly the same code.

Additionally, your patch masks a bug (derefencing uninitialized
memory). I will send a patch set shortly.

Regards
Stefan

  reply	other threads:[~2022-05-06 11:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-25 10:25 [PATCH] tpm: Add check for Failure mode for TPM2 modules Mårten Lindahl
2022-04-25 14:03 ` Jarkko Sakkinen
2022-04-25 15:52   ` Marten Lindahl
2022-05-06 12:00     ` Stefan Mahnke-Hartmann [this message]
2022-05-09 13:47       ` Marten Lindahl
2022-05-30 15:26     ` Marten Lindahl
2022-06-01  2:05       ` Jarkko Sakkinen
2022-06-02 11:15         ` Jarkko Sakkinen
2022-06-20 14:59           ` Marten Lindahl

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=20220506120041.228769-1-stefan.mahnke-hartmann@infineon.com \
    --to=stefan.mahnke-hartmann@infineon.com \
    --cc=Marten.Lindahl@axis.com \
    --cc=jarkko@kernel.org \
    --cc=jgg@ziepe.ca \
    --cc=kernel@axis.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=martenli@axis.com \
    --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 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.