linux-kernel - Re: [PATCH v4 0/3] tpm: Fix TPM 1.2 Shutdown sequence to prevent future TPM operations

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20191014103926.GB12301@linux.intel.com>
Date:   Mon, 14 Oct 2019 13:39:26 +0300
From:   Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
To:     Greg KH <gregkh@...uxfoundation.org>
Cc:     linux-stable@...r.kernel.org, linux-integrity@...r.kernel.org,
        Vadim Sukhomlinov <sukhomlinov@...gle.com>,
        Jason Gunthorpe <jgg@...pe.ca>,
        open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v4 0/3] tpm: Fix TPM 1.2 Shutdown sequence to prevent
 future TPM operations

On Thu, Oct 10, 2019 at 10:28:22AM +0200, Greg KH wrote:
> On Thu, Oct 10, 2019 at 12:28:28AM +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.
> 
> How can a 0/X have a git commit id?
> 
> :)
> 
> greg k-h

It cannot. I just mentioned it here because the whole purpose
of two other dependecies is to support the backport of that
upstream commit.

/Jarkko.