From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Doug Anderson <dianders@chromium.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Vadim Sukhomlinov <sukhomlinov@google.com>,
"# 4.0+" <stable@vger.kernel.org>
Subject: Re: FAILED: patch "[PATCH] tpm: Fix TPM 1.2 Shutdown sequence to prevent future TPM" failed to apply to 4.19-stable tree
Date: Fri, 12 Jul 2019 05:57:06 +0300 [thread overview]
Message-ID: <20190712025706.2psp65fippc67c2p@linux.intel.com> (raw)
In-Reply-To: <CAD=FV=UCqRpSsMpastf8K9nZukST6h8qjn2ofAQsJU00EyW5EA@mail.gmail.com>
On Thu, Jul 11, 2019 at 11:49:10AM -0700, Doug Anderson wrote:
> Hi,
>
> On Thu, Jul 11, 2019 at 11:17 AM Jarkko Sakkinen
> <jarkko.sakkinen@linux.intel.com> wrote:
> >
> > On Thu, Jul 11, 2019 at 09:30:25AM -0700, Doug Anderson wrote:
> > > Hi,
> > >
> > > On Thu, Jul 11, 2019 at 4:35 AM <gregkh@linuxfoundation.org> wrote:
> > > >
> > > >
> > > > The patch below does not apply to the 4.19-stable tree.
> > > > If someone wants it applied there, or to any other stable or longterm
> > > > tree, then please email the backport, including the original git commit
> > > > id to <stable@vger.kernel.org>.
> > > >
> > > > thanks,
> > > >
> > > > greg k-h
> > > >
> > > > ------------------ original commit in Linus's tree ------------------
> > > >
> > > > From db4d8cb9c9f2af71c4d087817160d866ed572cc9 Mon Sep 17 00:00:00 2001
> > > > From: Vadim Sukhomlinov <sukhomlinov@google.com>
> > > > Date: Mon, 10 Jun 2019 15:01:18 -0700
> > > > Subject: [PATCH] tpm: Fix TPM 1.2 Shutdown sequence to prevent future TPM
> > > > operations
> > >
> > > Posted at:
> > >
> > > https://lkml.kernel.org/r/20190711162919.23813-1-dianders@chromium.org
> >
> > Thank you! I usually end up taking care of these myself :-) A rare
> > occasion. Does this also address 4.4, 4.9 and 4.14 or do they still
> > need backports of their own?
>
> In Chrome OS we have the same solution for 4.14.
>
> This patch will _definitely_ not apply cleanly for 4.4. Not sure what
> the best course of action is there, but in the "after the cut" notes
> in my post I talk about it a little bit.
>
> On 4.9 things look similar-ish, but I don't know quite enough to know
> if it will work well there.
>
> (all of this in the context that apparently some extra locking patches
> even for 4.14 and 4.19--see the thread in response to my posted
> patch).
OK, I'll look at those when I come back from leave after two weeks.
/Jarkko
prev parent reply other threads:[~2019-07-12 2:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 11:35 FAILED: patch "[PATCH] tpm: Fix TPM 1.2 Shutdown sequence to prevent future TPM" failed to apply to 4.19-stable tree gregkh
2019-07-11 16:30 ` Doug Anderson
2019-07-11 18:17 ` Jarkko Sakkinen
2019-07-11 18:49 ` Doug Anderson
2019-07-12 2:57 ` Jarkko Sakkinen [this message]
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=20190712025706.2psp65fippc67c2p@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=dianders@chromium.org \
--cc=gregkh@linuxfoundation.org \
--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 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.