summaryrefslogtreecommitdiff
path: root/fs/cifs
diff options
context:
space:
mode:
authorChuck Lever <chuck.lever@oracle.com>2019-11-21 00:25:52 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2020-10-01 14:17:21 +0300
commit3ce5297c0b40a01e8f1e2c4bf6bc2944ec21439f (patch)
tree1409ee53040cb52dd4af8f017c48a132d738b6db /fs/cifs
parent80f7667422447a146f55b26e7b453354cccdc642 (diff)
downloadlinux-3ce5297c0b40a01e8f1e2c4bf6bc2944ec21439f.tar.xz
SUNRPC: Capture completion of all RPC tasks
[ Upstream commit a264abad51d8ecb7954a2f6d9f1885b38daffc74 ] RPC tasks on the backchannel never invoke xprt_complete_rqst(), so there is no way to report their tk_status at completion. Also, any RPC task that exits via rpc_exit_task() before it is replied to will also disappear without a trace. Introduce a trace point that is symmetrical with rpc_task_begin that captures the termination status of each RPC task. Sample trace output for callback requests initiated on the server: kworker/u8:12-448 [003] 127.025240: rpc_task_end: task:50@3 flags=ASYNC|DYNAMIC|SOFT|SOFTCONN|SENT runstate=RUNNING|ACTIVE status=0 action=rpc_exit_task kworker/u8:12-448 [002] 127.567310: rpc_task_end: task:51@3 flags=ASYNC|DYNAMIC|SOFT|SOFTCONN|SENT runstate=RUNNING|ACTIVE status=0 action=rpc_exit_task kworker/u8:12-448 [001] 130.506817: rpc_task_end: task:52@3 flags=ASYNC|DYNAMIC|SOFT|SOFTCONN|SENT runstate=RUNNING|ACTIVE status=0 action=rpc_exit_task Odd, though, that I never see trace_rpc_task_complete, either in the forward or backchannel. Should it be removed? Signed-off-by: Chuck Lever <chuck.lever@oracle.com> Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com> Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'fs/cifs')
0 files changed, 0 insertions, 0 deletions