]> asedeno.scripts.mit.edu Git - linux.git/commit
SUNRPC: task_run_action should display tk_callback
authorChuck Lever <chuck.lever@oracle.com>
Wed, 3 Jan 2018 20:38:41 +0000 (15:38 -0500)
committerAnna Schumaker <Anna.Schumaker@Netapp.com>
Tue, 23 Jan 2018 14:44:40 +0000 (09:44 -0500)
commitcf08d6f2e6e1b9f177cafbe57e7ad33a76d32c38
tree679853991278da95a96b937fa80ecc3ef199f2da
parent520694496aec9c4f1f69f8400753f04a6ffdbfc5
SUNRPC: task_run_action should display tk_callback

This shows up in every RPC:

     kworker/4:1-19772 [004]  3467.373443: rpc_task_run_action:  task:4711@2 flags=0e81 state=0005 status=0 action=call_status
     kworker/4:1-19772 [004]  3467.373444: rpc_task_run_action:  task:4711@2 flags=0e81 state=0005 status=0 action=call_status

What's actually going on is that the first iteration of the RPC
scheduler is invoking the function in tk_callback (in this case,
xprt_timer), then invoking call_status on the next iteration.

Feeding do_action, rather than tk_action, to the "task_run_action"
trace point will now always display the correct FSM step.

Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com>
net/sunrpc/sched.c