diff options
author | Matt Fleming <matt@codeblueprint.co.uk> | 2016-02-15 10:34:05 +0000 |
---|---|---|
committer | Matt Fleming <matt@codeblueprint.co.uk> | 2016-02-16 12:48:18 +0000 |
commit | e246eb568bc4cbbdd8a30a3c11151ff9b7ca7312 (patch) | |
tree | 370afd77aa3621bfd8fe11139951d5c729bcbc68 /lib | |
parent | 4682c211a80ee93214b72d95f861b0f6e90e5445 (diff) | |
download | talos-obmc-linux-e246eb568bc4cbbdd8a30a3c11151ff9b7ca7312.tar.gz talos-obmc-linux-e246eb568bc4cbbdd8a30a3c11151ff9b7ca7312.zip |
efi: Add pstore variables to the deletion whitelist
Laszlo explains why this is a good idea,
'This is because the pstore filesystem can be backed by UEFI variables,
and (for example) a crash might dump the last kilobytes of the dmesg
into a number of pstore entries, each entry backed by a separate UEFI
variable in the above GUID namespace, and with a variable name
according to the above pattern.
Please see "drivers/firmware/efi/efi-pstore.c".
While this patch series will not prevent the user from deleting those
UEFI variables via the pstore filesystem (i.e., deleting a pstore fs
entry will continue to delete the backing UEFI variable), I think it
would be nice to preserve the possibility for the sysadmin to delete
Linux-created UEFI variables that carry portions of the crash log,
*without* having to mount the pstore filesystem.'
There's also no chance of causing machines to become bricked by
deleting these variables, which is the whole purpose of excluding
things from the whitelist.
Use the LINUX_EFI_CRASH_GUID guid and a wildcard '*' for the match so
that we don't have to update the string in the future if new variable
name formats are created for crash dump variables.
Reported-by: Laszlo Ersek <lersek@redhat.com>
Acked-by: Peter Jones <pjones@redhat.com>
Tested-by: Peter Jones <pjones@redhat.com>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: "Lee, Chun-Yi" <jlee@suse.com>
Signed-off-by: Matt Fleming <matt@codeblueprint.co.uk>
Diffstat (limited to 'lib')
0 files changed, 0 insertions, 0 deletions