summaryrefslogtreecommitdiff
path: root/fs/jffs2/README.Locking
diff options
context:
space:
mode:
authorArd Biesheuvel <ard.biesheuvel@linaro.org>2017-03-01 22:04:35 +0300
committerIngo Molnar <mingo@kernel.org>2017-03-02 10:11:18 +0300
commit52e51f16407b7b34e26affb500a21e250d9fce0b (patch)
tree657dbdb683203334bcbaf0d024528249aa376645 /fs/jffs2/README.Locking
parent4977ab6e92e267afe9d8f78438c3db330ca8434c (diff)
downloadlinux-52e51f16407b7b34e26affb500a21e250d9fce0b.tar.xz
efi/libstub: Treat missing SecureBoot variable as Secure Boot disabled
The newly refactored code that infers the firmware's Secure Boot state prints the following error when the EFI variable 'SecureBoot' does not exist: EFI stub: ERROR: Could not determine UEFI Secure Boot status. However, this variable is only guaranteed to be defined on a system that is Secure Boot capable to begin with, and so it is not an error if it is missing. So report Secure Boot as being disabled in this case, without printing any error messages. Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Matt Fleming <matt@codeblueprint.co.uk> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: linux-efi@vger.kernel.org Link: http://lkml.kernel.org/r/1488395076-29712-2-git-send-email-ard.biesheuvel@linaro.org Signed-off-by: Ingo Molnar <mingo@kernel.org>
Diffstat (limited to 'fs/jffs2/README.Locking')
0 files changed, 0 insertions, 0 deletions