diff options
author | Eric Richter <erichte@linux.ibm.com> | 2020-09-16 11:21:15 -0500 |
---|---|---|
committer | Oliver O'Halloran <oohall@gmail.com> | 2020-10-01 13:44:06 +1000 |
commit | b3a13fea4f57df9ce2b0c91f91a30d12af38b358 (patch) | |
tree | 6759019edb9502121ea0856dbaff4beb61bef1b4 /Makefile.rules | |
parent | 40f62c927a3ebd1a32b6900715ef42ffd401e4b9 (diff) | |
download | skiboot-b3a13fea4f57df9ce2b0c91f91a30d12af38b358.zip skiboot-b3a13fea4f57df9ce2b0c91f91a30d12af38b358.tar.gz skiboot-b3a13fea4f57df9ce2b0c91f91a30d12af38b358.tar.bz2 |
secvar_main: rework secvar_main error flow, make storage locking explicit
This patch adjusts the behavior of secvar_main to actually halt the boot
in some form if there is an issue initializing secure variables. The secvar
storage driver contains the secure boot state, and therefore if that fails
to initialize, we immediately need to halt the boot. For all other cases we
enforce secure boot in the bootloader by setting the secure mode flag, but
booting with an empty keyring (and thus, cannot verify a kexec image).
Previously, the storage driver was expected to handle any locking
procedures implicitly as part of the write operation. This patch uses the
new lockdown hook which makes locking explicit and part of the secvar_main
flow.
The storage driver is now locked unconditionally when exiting
secvar_main, and the lockdown() call should halt the boot if it encounters
any sign of struggle.
Signed-off-by: Eric Richter <erichte@linux.ibm.com>
Signed-off-by: Oliver O'Halloran <oohall@gmail.com>
Diffstat (limited to 'Makefile.rules')
0 files changed, 0 insertions, 0 deletions