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/locking/lockdep.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/kernel/locking/lockdep.c b/kernel/locking/lockdep.c index 81f1a71..ea9ca31 100644 --- a/kernel/locking/lockdep.c +++ b/kernel/locking/lockdep.c @@ -56,14 +56,14 @@ #ifdef CONFIG_PROVE_LOCKING int prove_locking = 1; -module_param(prove_locking, int, 0644); +module_param(prove_locking, int, S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH); #else #define prove_locking 0 #endif #ifdef CONFIG_LOCK_STAT int lock_stat = 1; -module_param(lock_stat, int, 0644); +module_param(lock_stat, int, S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH); #else #define lock_stat 0 #endif -- 2.9.2
