forked from Minki/linux
nfsd: Log client tracking type log message as info instead of warning
`printk()`, by default, uses the log level warning, which leaves the user reading NFSD: Using UMH upcall client tracking operations. wondering what to do about it (`dmesg --level=warn`). Several client tracking methods are tried, and expected to fail. That’s why a message is printed only on success. It might be interesting for users to know the chosen method, so use info-level instead of debug-level. Cc: linux-nfs@vger.kernel.org Signed-off-by: Paul Menzel <pmenzel@molgen.mpg.de> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
This commit is contained in:
parent
7f7e7a4006
commit
f988a7b71d
@ -626,7 +626,7 @@ nfsd4_legacy_tracking_init(struct net *net)
|
||||
status = nfsd4_load_reboot_recovery_data(net);
|
||||
if (status)
|
||||
goto err;
|
||||
printk("NFSD: Using legacy client tracking operations.\n");
|
||||
pr_info("NFSD: Using legacy client tracking operations.\n");
|
||||
return 0;
|
||||
|
||||
err:
|
||||
@ -1028,7 +1028,7 @@ nfsd4_init_cld_pipe(struct net *net)
|
||||
|
||||
status = __nfsd4_init_cld_pipe(net);
|
||||
if (!status)
|
||||
printk("NFSD: Using old nfsdcld client tracking operations.\n");
|
||||
pr_info("NFSD: Using old nfsdcld client tracking operations.\n");
|
||||
return status;
|
||||
}
|
||||
|
||||
@ -1605,7 +1605,7 @@ nfsd4_cld_tracking_init(struct net *net)
|
||||
nfs4_release_reclaim(nn);
|
||||
goto err_remove;
|
||||
} else
|
||||
printk("NFSD: Using nfsdcld client tracking operations.\n");
|
||||
pr_info("NFSD: Using nfsdcld client tracking operations.\n");
|
||||
return 0;
|
||||
|
||||
err_remove:
|
||||
@ -1864,7 +1864,7 @@ nfsd4_umh_cltrack_init(struct net *net)
|
||||
ret = nfsd4_umh_cltrack_upcall("init", NULL, grace_start, NULL);
|
||||
kfree(grace_start);
|
||||
if (!ret)
|
||||
printk("NFSD: Using UMH upcall client tracking operations.\n");
|
||||
pr_info("NFSD: Using UMH upcall client tracking operations.\n");
|
||||
return ret;
|
||||
}
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user