For troubleshooting, it is useful to show the callback address and state inside the nfsd4 client info. Note the callback address and state is also available via trace events, so use a common function and output. Changes since v1: - fix indents, run checkpatch (Chuck L) - create cb_state2str() inside fs/nfsd/trace.c (Bruce F) - rebase on Chuck v3 nfsd patches and test Dave Wysochanski (1): nfsd4: Expose the callback address and state of each NFS4 client fs/nfsd/nfs4state.c | 2 ++ fs/nfsd/trace.c | 15 +++++++++++++++ fs/nfsd/trace.h | 9 ++------- 3 files changed, 19 insertions(+), 7 deletions(-) -- 1.8.3.1
