kernel_module_vfat_disabled: limit to non-uefi - #13883
Conversation
Currently kernel_module_vfat_disabled is low or failed on systems with a kernel. However, on UEFI platforms VFAT is required to access ESP and is typically built-in. Blocking modprobe of it is a no-op, and VFAT usage is required on such systems. Thus limit the platform of this rule to non-uefi systems, as only on those platforms one can realistically run without VFAT support. Another option is to remove this rule entirely. Many distributions make VFAT built-in even on those architectures / platforms that do not use VFAT for booting.
|
Hi @xnox. Thanks for your PR. I'm waiting for a ComplianceAsCode member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@jan-cerny are you able to trigger the |
2 participants
Currently kernel_module_vfat_disabled is low or failed on systems with
a kernel. However, on UEFI platforms VFAT is required to access ESP
and is typically built-in. Blocking modprobe of it is a no-op, and
VFAT usage is required on such systems.
Thus limit the platform of this rule to non-uefi systems, as only on
those platforms one can realistically run without VFAT support.
Another option is to remove this rule entirely. Many distributions
make VFAT built-in even on those architectures / platforms that do not
use VFAT for booting.