From: David Howells <dhowells@redhat.com>
To: unlisted-recipients:; (no To-header on input)
Cc: dhowells@redhat.com, matt@codeblueprint.co.uk,
ard.biesheuvel@linaro.org, linux-efi@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, keyrings@vger.kernel.org
Subject: Re: [PATCH 5/8] efi: Get the secure boot status [ver #4]
Date: Wed, 07 Dec 2016 11:49:02 +0000 [thread overview]
Message-ID: <12379.1481111342@warthog.procyon.org.uk> (raw)
In-Reply-To: <148110911515.11513.12993373251483766180.stgit@warthog.procyon.org.uk>
David Howells <dhowells@redhat.com> wrote:
> index d85b9625e836..c418ccc8c98e 100644
> --- a/arch/x86/boot/compressed/head_32.S
> +++ b/arch/x86/boot/compressed/head_32.S
> @@ -61,6 +61,7 @@
>
> __HEAD
> ENTRY(startup_32)
> + movb $0, BP_secure_boot(%rsi)
> #ifdef CONFIG_EFI_STUB
> jmp preferred_addr
>
Bah. Forgot to compile for i386. Will repost.
David
prev parent reply other threads:[~2016-12-07 11:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 11:11 [PATCH 0/8] efi: Pass secure boot mode to kernel " David Howells
2016-12-07 11:11 ` [PATCH 1/8] efi: use typed function pointers for runtime services table " David Howells
2016-12-07 11:11 ` [PATCH 2/8] x86/efi: Allow invocation of arbitrary runtime services " David Howells
2016-12-07 11:11 ` [PATCH 3/8] arm/efi: " David Howells
2016-12-07 11:11 ` [PATCH 4/8] efi: Add SHIM and image security database GUID definitions " David Howells
2016-12-07 11:11 ` [PATCH 5/8] efi: Get the secure boot status " David Howells
2016-12-07 11:12 ` [PATCH 6/8] efi: Disable secure boot if shim is in insecure mode " David Howells
2016-12-07 11:12 ` [PATCH 7/8] efi: Add EFI_SECURE_BOOT bit " David Howells
2016-12-07 11:12 ` [PATCH 8/8] efi: Handle secure boot from UEFI-2.6 " David Howells
2016-12-07 11:49 ` David Howells [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=12379.1481111342@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=ard.biesheuvel@linaro.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome