rxrpc: Unlock new call in rxrpc_new_incoming_call() rather than the caller
authorDavid Howells <dhowells@redhat.com>
Wed, 18 Dec 2019 16:38:49 +0000 (16:38 +0000)
committerDavid Howells <dhowells@redhat.com>
Fri, 20 Dec 2019 16:20:48 +0000 (16:20 +0000)
commitf33121cbe91973a08e68e4bde8c3f7e6e4e351c1
tree29a7d330b0a1b37db09e515e652a925820b088ed
parent615f22f58029aa747b12768985e7f91cd053daa2
rxrpc: Unlock new call in rxrpc_new_incoming_call() rather than the caller

Move the unlock and the ping transmission for a new incoming call into
rxrpc_new_incoming_call() rather than doing it in the caller.  This makes
it clearer to see what's going on.

Suggested-by: Peter Zijlstra <peterz@infradead.org>
Signed-off-by: David Howells <dhowells@redhat.com>
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
cc: Ingo Molnar <mingo@redhat.com>
cc: Will Deacon <will@kernel.org>
cc: Davidlohr Bueso <dave@stgolabs.net>
net/rxrpc/call_accept.c
net/rxrpc/input.c