I find that the developers often just specified the numeric value when calling a macro which is defined with a parameter for access permission. As we know, these numeric value for access permission have had the corresponding macro, and that using macro can improve the robustness and readability of the code, thus, I suggest replacing the numeric parameter with the macro.
Signed-off-by: Chuansheng Liu <chuansheng....@intel.com> Signed-off-by: Baole Ni <baolex...@intel.com> --- kernel/module.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/module.c b/kernel/module.c index 5f71aa6..58ddf54 100644 --- a/kernel/module.c +++ b/kernel/module.c @@ -271,7 +271,7 @@ static void module_assert_mutex_or_preempt(void) static bool sig_enforce = IS_ENABLED(CONFIG_MODULE_SIG_FORCE); #ifndef CONFIG_MODULE_SIG_FORCE -module_param(sig_enforce, bool_enable_only, 0644); +module_param(sig_enforce, bool_enable_only, S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH); #endif /* !CONFIG_MODULE_SIG_FORCE */ /* Block module loading/unloading? */ -- 2.9.2
