Patch "rxrpc: The mutex lock returned by rxrpc_accept_call() needs releasing" has been added to the 4.14-stable tree
Subsystems (3)
This is a note to let you know that I've just added the patch titled
rxrpc: The mutex lock returned by rxrpc_accept_call() needs releasing
to the 4.14-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
rxrpc-the-mutex-lock-returned-by-rxrpc_accept_call-needs-releasing.patch
and it can be found in the queue-4.14 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree, please let <[email protected]> know about it.
Quoted 1 line
From foo@baz Thu Feb 1 13:45:42 CET 2018
From: David Howells <[email protected]>
Date: Fri, 24 Nov 2017 10:18:40 +0000
Subject: rxrpc: The mutex lock returned by rxrpc_accept_call() needs releasing
From: David Howells <[email protected]>
[ Upstream commit 03a6c82218b9a87014b2c6c4e178294fdc8ebd8a ]
The caller of rxrpc_accept_call() must release the lock on call->user_mutex returned by that function.
--- net/rxrpc/sendmsg.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
net/rxrpc/sendmsg.c +3 -2
@@ -563,8 +563,8 @@ int rxrpc_do_sendmsg(struct rxrpc_sock */* The socket is now unlocked. */ if (IS_ERR (call))return PTR_ERR (call); -rxrpc_put_call (call, rxrpc_call_put); -return 0 ; + ret =0 ; + goto out_put_unlock; } call =rxrpc_find_call_by_user_ID (rx, p.user_call_ID);
@@ -633,6 +633,7 @@ int rxrpc_do_sendmsg(struct rxrpc_sock * ret =rxrpc_send_data (rx, call, msg, len,NULL ); } +out_put_unlock:mutex_unlock (&call->user_mutex); error_put:rxrpc_put_call (call, rxrpc_call_put);
Patches currently in stable-queue which might be from [email protected] are
queue-4.14/rxrpc-the-mutex-lock-returned-by-rxrpc_accept_call-needs-releasing.patch queue-4.14/rxrpc-provide-a-different-lockdep-key-for-call-user_mutex-for-kernel-calls.patch queue-4.14/rxrpc-fix-service-endpoint-expiry.patch