diff options
author | David S. Miller <davem@davemloft.net> | 2019-12-25 03:12:47 +0300 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2019-12-25 03:12:47 +0300 |
commit | ff43ae4bd5aab8acd3a4a9cf49a2a99cbb1719fb (patch) | |
tree | e76dfc52bb66f7d702087da1da3da0ed191a2f4f /net/bridge | |
parent | 7c3125f0a6ebc17846c5908ad7d6056d66c1c426 (diff) | |
parent | 063c60d39180cec7c9317f5acfc3071f8fecd705 (diff) | |
download | linux-ff43ae4bd5aab8acd3a4a9cf49a2a99cbb1719fb.tar.xz |
Merge tag 'rxrpc-fixes-20191220' of git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs
David Howells says:
====================
rxrpc: Fixes
Here are a couple of bugfixes plus a patch that makes one of the bugfixes
easier:
(1) Move the ping and mutex unlock on a new call from rxrpc_input_packet()
into rxrpc_new_incoming_call(), which it calls. This means the
lock-unlock section is entirely within the latter function. This
simplifies patch (2).
(2) Don't take the call->user_mutex at all in the softirq path. Mutexes
aren't allowed to be taken or released there and a patch was merged
that caused a warning to be emitted every time this happened. Looking
at the code again, it looks like that taking the mutex isn't actually
necessary, as the value of call->state will block access to the call.
(3) Fix the incoming call path to check incoming calls earlier to reject
calls to RPC services for which we don't have a security key of the
appropriate class. This avoids an assertion failure if YFS tries
making a secure call to the kafs cache manager RPC service.
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/bridge')
0 files changed, 0 insertions, 0 deletions