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 <[email protected]>
Signed-off-by: Baole Ni <[email protected]>
---
 fs/nfs/flexfilelayout/flexfilelayoutdev.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/fs/nfs/flexfilelayout/flexfilelayoutdev.c 
b/fs/nfs/flexfilelayout/flexfilelayoutdev.c
index 0aa36be..e76c3a7 100644
--- a/fs/nfs/flexfilelayout/flexfilelayoutdev.c
+++ b/fs/nfs/flexfilelayout/flexfilelayoutdev.c
@@ -563,11 +563,11 @@ bool ff_layout_avoid_read_on_rw(struct 
pnfs_layout_segment *lseg)
               ff_layout_no_read_on_rw(lseg);
 }
 
-module_param(dataserver_retrans, uint, 0644);
+module_param(dataserver_retrans, uint, S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH);
 MODULE_PARM_DESC(dataserver_retrans, "The  number of times the NFSv4.1 client "
                        "retries a request before it attempts further "
                        " recovery  action.");
-module_param(dataserver_timeo, uint, 0644);
+module_param(dataserver_timeo, uint, S_IRUSR | S_IWUSR | S_IRGRP | S_IROTH);
 MODULE_PARM_DESC(dataserver_timeo, "The time (in tenths of a second) the "
                        "NFSv4.1  client  waits for a response from a "
                        " data server before it retries an NFS request.");
-- 
2.9.2

Reply via email to