Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1454543 > unrolled thread

[PATCH 1066/1285] Replace numeric parameter like 0444 with macro

Back to article view | Back to linux.kernel

Contents

  [PATCH 1066/1285] Replace numeric parameter like 0444 with macro Baole Ni <baolex.ni@intel.com> - 2016-08-02 16:30 +0200

#1454543 — [PATCH 1066/1285] Replace numeric parameter like 0444 with macro

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.liu@intel.com>
Signed-off-by: Baole Ni <baolex.ni@intel.com>
---
 kernel/locking/locktorture.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/kernel/locking/locktorture.c b/kernel/locking/locktorture.c
index f8c5af5..265030a 100644
--- a/kernel/locking/locktorture.c
+++ b/kernel/locking/locktorture.c
@@ -59,7 +59,7 @@ torture_param(bool, verbose, true,
 	     "Enable verbose debugging printk()s");
 
 static char *torture_type = "spin_lock";
-module_param(torture_type, charp, 0444);
+module_param(torture_type, charp, S_IRUSR | S_IRGRP | S_IROTH);
 MODULE_PARM_DESC(torture_type,
 		 "Type of lock to torture (spin_lock, spin_lock_irq, mutex_lock, ...)");
 
@@ -76,7 +76,7 @@ struct lock_stress_stats {
 };
 
 int torture_runnable = IS_ENABLED(MODULE);
-module_param(torture_runnable, int, 0444);
+module_param(torture_runnable, int, S_IRUSR | S_IRGRP | S_IROTH);
 MODULE_PARM_DESC(torture_runnable, "Start locktorture at module init");
 
 /* Forward reference. */
-- 
2.9.2

[toc] | [standalone]

Back to top | Article view | linux.kernel

csiph-web