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;
Date:   Sat, 31 Mar 2018 11:46:10 +1100 (AEDT)
From:   James Morris <jmorris@namei.org>
To:     David Howells <dhowells@redhat.com>
cc:     gnomes@lxorguk.ukuu.org.uk, linux-efi@vger.kernel.org,
        mjg59@google.com, gregkh@linuxfoundation.org,
        linux-kernel@vger.kernel.org, jforbes@redhat.com,
        linux-man@vger.kernel.org, jlee@suse.com,
        linux-security-module@vger.kernel.org
Subject: Re: [GIT PULL] Kernel lockdown for secure boot
In-Reply-To: <4136.1522452584@warthog.procyon.org.uk>
Message-ID: <alpine.LRH.2.21.1803311145180.7769@namei.org>
References: <4136.1522452584@warthog.procyon.org.uk>
User-Agent: Alpine 2.21 (LRH 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Sat, 31 Mar 2018, David Howells wrote:

> Date: Thu, 26 Oct 2017 17:37:38 +0100
> 
> Hi James,
> 
> Can you pull this patchset into security/next please?  It has been in
> linux-next since the beginning of March.
> 
> It adds kernel lockdown support for EFI secure boot.

Applied to
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git 
next-lockdown and next-testing

Are there any known coverage gaps now?


-- 
James Morris
<jmorris@namei.org>