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)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Fri, 17 Jan 2020 18:49:05 +0000 (19:49 +0100)
commit344b0d8abf2291d690400f1383ff1cdb35dd6251
tree8bff8d02f290b6430557fa98ce82d2c3066401a4
parentf54802bfc97bff552ec4781293f37f7e26be229e
rxrpc: Unlock new call in rxrpc_new_incoming_call() rather than the caller

[ Upstream commit f33121cbe91973a08e68e4bde8c3f7e6e4e351c1 ]

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>
Signed-off-by: Sasha Levin <sashal@kernel.org>
net/rxrpc/call_accept.c
net/rxrpc/input.c