linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Chester Lin <clin@suse.com>
To: ardb@kernel.org, catalin.marinas@arm.com, will@kernel.org,
	zohar@linux.ibm.com, dmitry.kasatkin@gmail.com, corbet@lwn.net,
	mark.rutland@arm.com, vincenzo.frascino@arm.com,
	samitolvanen@google.com, masahiroy@kernel.org, mingo@kernel.org
Cc: clin@suse.com, linux-efi@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	jlee@suse.com, linux-integrity@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/6] efi: add secure boot flag
Date: Fri,  4 Sep 2020 15:29:02 +0800	[thread overview]
Message-ID: <20200904072905.25332-4-clin@suse.com> (raw)
In-Reply-To: <20200904072905.25332-1-clin@suse.com>

Add a new EFI flag to indicate whether secure boot is enabled by UEFI
firmware or not.

Signed-off-by: Chester Lin <clin@suse.com>
---
 include/linux/efi.h | 1 +
 1 file changed, 1 insertion(+)

diff --git a/include/linux/efi.h b/include/linux/efi.h
index 315126b2f5e9..82a19bb0237a 100644
--- a/include/linux/efi.h
+++ b/include/linux/efi.h
@@ -784,6 +784,7 @@ extern int __init efi_setup_pcdp_console(char *);
 #define EFI_MEM_ATTR		10	/* Did firmware publish an EFI_MEMORY_ATTRIBUTES table? */
 #define EFI_MEM_NO_SOFT_RESERVE	11	/* Is the kernel configured to ignore soft reservations? */
 #define EFI_PRESERVE_BS_REGIONS	12	/* Are EFI boot-services memory segments available? */
+#define EFI_SECURE_BOOT		13	/* Is EFI secure-boot enabled? */
 
 #ifdef CONFIG_EFI
 /*
-- 
2.26.1


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2020-09-04  7:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-04  7:28 [PATCH 0/6] add ima_arch support for ARM64 Chester Lin
2020-09-04  7:29 ` [PATCH 1/6] efistub: pass uefi secureboot flag via fdt params Chester Lin
2020-09-11 15:01   ` Ard Biesheuvel
2020-09-14  8:05     ` Chester Lin
2020-10-05  2:20       ` Chester Lin
2020-10-12  8:20         ` Ard Biesheuvel
2020-09-04  7:29 ` [PATCH 2/6] efi/arm: a helper to parse secure boot param in " Chester Lin
2020-09-04  7:29 ` Chester Lin [this message]
2020-09-04  7:29 ` [PATCH 4/6] efi/arm: check secure boot status in efi init Chester Lin
2020-09-04  7:29 ` [PATCH 5/6] arm64/ima: add ima arch support Chester Lin
2020-09-04 11:47   ` Mimi Zohar
2020-09-04  7:29 ` [PATCH 6/6] docs/arm: add the description of uefi-secure-boot param Chester Lin

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=20200904072905.25332-4-clin@suse.com \
    --to=clin@suse.com \
    --cc=ardb@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=corbet@lwn.net \
    --cc=dmitry.kasatkin@gmail.com \
    --cc=jlee@suse.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=masahiroy@kernel.org \
    --cc=mingo@kernel.org \
    --cc=samitolvanen@google.com \
    --cc=vincenzo.frascino@arm.com \
    --cc=will@kernel.org \
    --cc=zohar@linux.ibm.com \
    /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;
as well as URLs for NNTP newsgroup(s).