linux-integrity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: linux-integrity@vger.kernel.org,
	Vadim Sukhomlinov <sukhomlinov@google.com>,
	stable@vger.kernel.org, Douglas Anderson <dianders@chromium.org>,
	Peter Huewe <peterhuewe@gmx.de>, Jason Gunthorpe <jgg@ziepe.ca>,
	Arnd Bergmann <arnd@arndb.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] tpm: Fix TPM 1.2 Shutdown sequence to prevent future TPM operations
Date: Thu, 26 Sep 2019 19:22:25 -0400	[thread overview]
Message-ID: <20190926232225.GJ8171@sasha-vm> (raw)
In-Reply-To: <20190925101532.31280-4-jarkko.sakkinen@linux.intel.com>

On Wed, Sep 25, 2019 at 01:15:32PM +0300, Jarkko Sakkinen wrote:
>From: Vadim Sukhomlinov <sukhomlinov@google.com>
>
>commit db4d8cb9c9f2af71c4d087817160d866ed572cc9 upstream
>
>TPM 2.0 Shutdown involve sending TPM2_Shutdown to TPM chip and disabling
>future TPM operations. TPM 1.2 behavior was different, future TPM
>operations weren't disabled, causing rare issues. This patch ensures
>that future TPM operations are disabled.
>
>Fixes: d1bd4a792d39 ("tpm: Issue a TPM2_Shutdown for TPM2 devices.")
>Cc: stable@vger.kernel.org
>Signed-off-by: Vadim Sukhomlinov <sukhomlinov@google.com>
>[dianders: resolved merge conflicts with mainline]
>Signed-off-by: Douglas Anderson <dianders@chromium.org>
>Reviewed-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
>Signed-off-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>

I've queued it up for 4.19 and 4.14, thanks!

--
Thanks,
Sasha

  reply	other threads:[~2019-09-26 23:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-25 10:15 [PATCH 0/3] tpm: Fix TPM 1.2 Shutdown sequence to prevent future TPM operations Jarkko Sakkinen
2019-09-25 10:15 ` [PATCH 1/3] tpm: migrate pubek_show to struct tpm_buf Jarkko Sakkinen
2019-09-25 10:15 ` [PATCH 2/3] tpm: use tpm_try_get_ops() in tpm-sysfs.c Jarkko Sakkinen
2019-09-25 10:15 ` [PATCH 3/3] tpm: Fix TPM 1.2 Shutdown sequence to prevent future TPM operations Jarkko Sakkinen
2019-09-26 23:22   ` Sasha Levin [this message]
2019-09-25 14:47 ` [PATCH 0/3] " Jarkko Sakkinen
  -- strict thread matches above, loose matches on Subject: below --
2019-10-03 11:24 Jarkko Sakkinen
2019-10-03 11:24 ` [PATCH 3/3] " Jarkko Sakkinen
2019-10-02 13:14 [PATCH 0/3] " Jarkko Sakkinen
2019-10-02 13:14 ` [PATCH 3/3] " Jarkko Sakkinen
2019-10-02 13:57   ` Greg KH
2019-10-02 15:17     ` Sasha Levin
2019-10-02 15:31       ` Jerry Snitselaar
2019-10-02 15:42         ` Jerry Snitselaar
2019-10-02 16:09           ` Greg KH
2019-10-03 11:24           ` Jarkko Sakkinen
2019-10-03 11:25             ` Jarkko Sakkinen
2019-09-24 14:01 [PATCH 0/3] " Jarkko Sakkinen
2019-09-24 14:02 ` [PATCH 3/3] " Jarkko Sakkinen

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=20190926232225.GJ8171@sasha-vm \
    --to=sashal@kernel.org \
    --cc=arnd@arndb.de \
    --cc=dianders@chromium.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jarkko.sakkinen@linux.intel.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterhuewe@gmx.de \
    --cc=stable@vger.kernel.org \
    --cc=sukhomlinov@google.com \
    /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).