Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <alpine.LRH.2.21.1810262033270.5228@namei.org>
In-Reply-To: <alpine.LRH.2.21.1810262033270.5228@namei.org>
From:   Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu, 1 Nov 2018 15:32:27 -0700
Message-ID: <CAHk-=wgiWxgsvmSs=BewWpfLB=vjCJ4U3yzaKzDsZVFA0L3Xtw@mail.gmail.com>
Subject: Re: [GIT PULL] security: keys updates for v4.20
To:     jmorris@namei.org
Cc:     linux-security-module@vger.kernel.org,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Fri, Oct 26, 2018 at 2:36 AM James Morris <jmorris@namei.org> wrote:
>
> From David: "Provide five new operations in the key_type struct that can
> be used to provide access to asymmetric key operations.  These will be
> implemented for the asymmetric key type in a later patch and may refer to
> a key retained in RAM by the kernel or a key retained in crypto hardware.

Pulled.

However. I really would have expected some of the TPM people to have
acked these, or at least looked at them. There was no sign of that in
any of the tpm commits that I could see..

Hmm?

               Linus