nfsd: rename delegation related tracepoints to make them less confusing
authorHou Tao <houtao1@huawei.com>
Fri, 28 Aug 2020 07:02:55 +0000 (15:02 +0800)
committerJ. Bruce Fields <bfields@redhat.com>
Fri, 25 Sep 2020 22:01:27 +0000 (18:01 -0400)
commit3caf91757ced158e6c4a44d8b105bd7b3e1767d8
tree08455fca76c15d4056dcae37f52ecb1232e88873
parentade3dbad1459e0a9a8ee8812925e0d968a2a5252
nfsd: rename delegation related tracepoints to make them less confusing

Now when a read delegation is given, two delegation related traces
will be printed:

    nfsd_deleg_open: client 5f45b854:e6058001 stateid 00000030:00000001
    nfsd_deleg_none: client 5f45b854:e6058001 stateid 0000002f:00000001

Although the intention is to let developers know two stateid are
returned, the traces are confusing about whether or not a read delegation
is handled out. So renaming trace_nfsd_deleg_none() to trace_nfsd_open()
and trace_nfsd_deleg_open() to trace_nfsd_deleg_read() to make
the intension clearer.

The patched traces will be:

    nfsd_deleg_read: client 5f48a967:b55b21cd stateid 00000003:00000001
    nfsd_open: client 5f48a967:b55b21cd stateid 00000002:00000001

Suggested-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: Hou Tao <houtao1@huawei.com>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
fs/nfsd/nfs4state.c
fs/nfsd/trace.h