From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: linux-stable@vger.kernel.org
Cc: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
Jason Gunthorpe <jgg@ziepe.ca>,
linux-integrity@vger.kernel.org (open list:TPM DEVICE DRIVER),
linux-kernel@vger.kernel.org (open list)
Subject: [PATCH 0/3] tpm: Fix TPM 1.2 Shutdown sequence to prevent future TPM operations
Date: Thu, 3 Oct 2019 14:24:21 +0300 [thread overview]
Message-ID: <20191003112424.9036-1-jarkko.sakkinen@linux.intel.com> (raw)
commit db4d8cb9c9f2af71c4d087817160d866ed572cc9 upstream
This backport is for v4.14 and v4.19 The backport requires non-racy
behaviour from TPM 1.x sysfs code. Thus, the dependecies for that
are included.
NOTE: 1/3 is only needed for v4.14.
v2:
* Something happened when merging 3/3 that write lock was taken
twice. Fixed in this version. Did also sanity check test with
TPM2:
echo devices > /sys/power/pm_test && echo mem > /sys/power/state
Jarkko Sakkinen (2):
tpm: migrate pubek_show to struct tpm_buf
tpm: use tpm_try_get_ops() in tpm-sysfs.c.
Vadim Sukhomlinov (1):
tpm: Fix TPM 1.2 Shutdown sequence to prevent future TPM operations
drivers/char/tpm/tpm-chip.c | 5 +-
drivers/char/tpm/tpm-sysfs.c | 201 +++++++++++++++++++++--------------
drivers/char/tpm/tpm.h | 13 ---
3 files changed, 124 insertions(+), 95 deletions(-)
--
2.20.1
next reply other threads:[~2019-10-03 11:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 11:24 Jarkko Sakkinen [this message]
2019-10-03 11:24 ` [PATCH 1/3] tpm: migrate pubek_show to struct tpm_buf Jarkko Sakkinen
2019-10-03 11:31 ` Greg Kroah-Hartman
2019-10-03 17:56 ` Jarkko Sakkinen
2019-10-03 11:24 ` [PATCH 2/3] tpm: use tpm_try_get_ops() in tpm-sysfs.c Jarkko Sakkinen
2019-10-03 11:24 ` [PATCH 3/3] tpm: Fix TPM 1.2 Shutdown sequence to prevent future TPM operations Jarkko Sakkinen
-- strict thread matches above, loose matches on Subject: below --
2019-10-02 13:14 [PATCH 0/3] " Jarkko Sakkinen
2019-09-25 10:15 Jarkko Sakkinen
2019-09-25 14:47 ` Jarkko Sakkinen
2019-09-24 14:01 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=20191003112424.9036-1-jarkko.sakkinen@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-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).