summaryrefslogtreecommitdiff
path: root/drivers/dax
diff options
context:
space:
mode:
authorArd Biesheuvel <ardb@kernel.org>2020-07-08 13:01:57 +0300
committerArd Biesheuvel <ardb@kernel.org>2020-07-09 10:14:29 +0300
commitf88814cc2578c121e6edef686365036db72af0ed (patch)
tree6e26f83eb19d95e6791b0aab4ef931ef75bb3286 /drivers/dax
parent3230d95cea0515a6acf3f5ff360663de4c40fd07 (diff)
efi/efivars: Expose RT service availability via efivars abstraction
Commit bf67fad19e493b ("efi: Use more granular check for availability for variable services") introduced a check into the efivarfs, efi-pstore and other drivers that aborts loading of the module if not all three variable runtime services (GetVariable, SetVariable and GetNextVariable) are supported. However, this results in efivarfs being unavailable entirely if only SetVariable support is missing, which is only needed if you want to make any modifications. Also, efi-pstore and the sysfs EFI variable interface could be backed by another implementation of the 'efivars' abstraction, in which case it is completely irrelevant which services are supported by the EFI firmware. So make the generic 'efivars' abstraction dependent on the availibility of the GetVariable and GetNextVariable EFI runtime services, and add a helper 'efivar_supports_writes()' to find out whether the currently active efivars abstraction supports writes (and wire it up to the availability of SetVariable for the generic one). Then, use the efivar_supports_writes() helper to decide whether to permit efivarfs to be mounted read-write, and whether to enable efi-pstore or the sysfs EFI variable interface altogether. Fixes: bf67fad19e493b ("efi: Use more granular check for availability for variable services") Reported-by: Heinrich Schuchardt <xypron.glpk@gmx.de> Acked-by: Ilias Apalodimas <ilias.apalodimas@linaro.org> Tested-by: Ilias Apalodimas <ilias.apalodimas@linaro.org> Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
Diffstat (limited to 'drivers/dax')
0 files changed, 0 insertions, 0 deletions