[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 9 Sep 2019 17:28:08 +0100
From: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
To: Sasha Levin <sashal@...nel.org>
Cc: Doug Anderson <dianders@...omium.org>,
LKML <linux-kernel@...r.kernel.org>,
"# 4.0+" <stable@...r.kernel.org>,
Vadim Sukhomlinov <sukhomlinov@...gle.com>,
linux-integrity@...r.kernel.org, Jason Gunthorpe <jgg@...pe.ca>
Subject: Re: [PATCH AUTOSEL 4.19 126/167] tpm: Fix TPM 1.2 Shutdown sequence
to prevent future TPM operations
On Sat, Sep 07, 2019 at 06:04:48PM -0400, Sasha Levin wrote:
> On Sat, Sep 07, 2019 at 09:55:18PM +0300, Jarkko Sakkinen wrote:
> > On Tue, 2019-09-03 at 15:43 -0400, Sasha Levin wrote:
> > > Right. I gave a go at backporting a few patches and this happens to be
> > > one of them. It will be a while before it goes in a stable tree
> > > (probably way after after LPC).
> >
> > It *semantically* depends on
> >
> > db4d8cb9c9f2 ("tpm: use tpm_try_get_ops() in tpm-sysfs.c.")
> >
> > I.e. can cause crashes without the above patch. As a code change your
> > patch is fine but it needs the above patch backported to work in stable
> > manner.
> >
> > So... either I can backport that one (because ultimately I have
> > responsibility to do that as the maintainer) but if you want to finish
> > this one that is what you need to backport in addition and then it
> > should be fine.
>
> If you're ok with the backport of this commit, I can just add
> db4d8cb9c9f2 on top.
Sure, I've already gave my promise to do that :-)
/Jarkko
Powered by blists - more mailing lists