From: Chuck Lever Date: Wed, 3 Jan 2018 20:38:41 +0000 (-0500) Subject: SUNRPC: task_run_action should display tk_callback X-Git-Tag: v4.19~1594^2~4^2~3 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=cf08d6f2e6e1b9f177cafbe57e7ad33a76d32c38;p=platform%2Fkernel%2Flinux-rpi.git 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 Signed-off-by: Anna Schumaker --- diff --git a/net/sunrpc/sched.c b/net/sunrpc/sched.c index b1b49ed..c292a5e 100644 --- a/net/sunrpc/sched.c +++ b/net/sunrpc/sched.c @@ -770,7 +770,7 @@ static void __rpc_execute(struct rpc_task *task) if (do_action == NULL) break; } - trace_rpc_task_run_action(task->tk_client, task, task->tk_action); + trace_rpc_task_run_action(task->tk_client, task, do_action); do_action(task); /*