From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: linux-integrity@vger.kernel.org
Cc: Greg KH <gregkh@linuxfoundation.org>,
Vadim Sukhomlinov <sukhomlinov@google.com>,
Jason Gunthorpe <jgg@ziepe.ca>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] tpm: Fix TPM 1.2 Shutdown sequence to prevent future TPM operations
Date: Wed, 25 Sep 2019 17:47:29 +0300 [thread overview]
Message-ID: <20190925144729.GB23867@linux.intel.com> (raw)
In-Reply-To: <20190925101532.31280-1-jarkko.sakkinen@linux.intel.com>
On Wed, Sep 25, 2019 at 01:15:29PM +0300, Jarkko Sakkinen wrote:
> 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.
>
> Cc: linux-integrity@vger.kernel.org
> Cc: Greg KH <gregkh@linuxfoundation.org>
> Cc: Vadim Sukhomlinov <sukhomlinov@google.com>
> Link: https://lore.kernel.org/stable/20190712152734.GA13940@kroah.com/
Resend by mistake.
/Jarkko
next prev parent reply other threads:[~2019-09-25 14:47 UTC|newest]
Thread overview: 9+ 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
2019-09-25 14:47 ` Jarkko Sakkinen [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-10-03 11:24 [PATCH 0/3] " Jarkko Sakkinen
2019-10-02 13:14 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=20190925144729.GB23867@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@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).