summaryrefslogtreecommitdiff
path: root/samples
diff options
context:
space:
mode:
authorGuilherme G. Piccoli <gpiccoli@igalia.com>2024-01-03 21:40:32 +0300
committerKees Cook <keescook@chromium.org>2024-02-22 21:37:21 +0300
commita28655c330ab294862cabe66deadb0f85cd4f191 (patch)
treeb67782643031b63498d14d61938bcb5009ae0679 /samples
parent77a6557d2a58ad9abea0537509d6dfc946cddfd3 (diff)
downloadlinux-a28655c330ab294862cabe66deadb0f85cd4f191.tar.xz
efi: pstore: Allow dynamic initialization based on module parameter
The efi-pstore module parameter "pstore_disable" warrants that users are able to deactivate such backend. There is also a Kconfig option for the default value of this parameter. It was originally added due to some bad UEFI FW implementations that could break with many variables written. Some distros (such as Arch Linux) set this in their config file still nowadays. And once it is set, even being a writable module parameter, there is effectively no way to make use of efi-pstore anymore. If "pstore_disable" is set to true, the init function of the module exits early and is never called again after the initcall processing. Let's switch this module parameter to have a callback and perform the pstore backend registration again each time it's set from Y->N (and vice-versa). With this, the writable nature of the parameter starts to make sense, given that users now can switch back to using efi-pstore or not during runtime by writing into it. Signed-off-by: Guilherme G. Piccoli <gpiccoli@igalia.com> Link: https://lore.kernel.org/r/20240103184053.226203-1-gpiccoli@igalia.com Signed-off-by: Kees Cook <keescook@chromium.org>
Diffstat (limited to 'samples')
0 files changed, 0 insertions, 0 deletions