NFS: Record task, client ID, and XID in xdr_status trace points
authorChuck Lever <chuck.lever@oracle.com>
Wed, 19 Jun 2019 14:34:09 +0000 (10:34 -0400)
committerAnna Schumaker <Anna.Schumaker@Netapp.com>
Tue, 9 Jul 2019 14:30:25 +0000 (10:30 -0400)
commit62a92ba97a31c544802bbf13d3a998e86796d548
treeabe58a8ec4901c2ce5d1a02bf8c6bda41fd245cf
parent7d4006c161ad8cded95f80f43b5fecc36e781497
NFS: Record task, client ID, and XID in xdr_status trace points

When triggering an nfs_xdr_status trace point, record the task ID
and XID of the failing RPC to better pinpoint the problem.

This feels like a bit of a layering violation.

Suggested-by: Trond Myklebust <trondmy@hammerspace.com>
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
fs/nfs/nfs2xdr.c
fs/nfs/nfs3xdr.c
fs/nfs/nfs4trace.h
fs/nfs/nfs4xdr.c
fs/nfs/nfstrace.h