rxrpc: Fix a case where a call event bit is being used as a flag bit

Fix a case where RXRPC_CALL_RELEASE (an event) is being used to specify a
flag bit.  RXRPC_CALL_RELEASED should be used instead.

Signed-off-by: David Howells <dhowells@redhat.com>

diff --git a/net/rxrpc/ar-accept.c b/net/rxrpc/ar-accept.c
index 6d79310fcaaeead0d6d0953f791e18385c794c03..65ea81399f6a924ea7b2a41e47af4a4a09186a5e 100644 (file)
--- a/net/rxrpc/ar-accept.c
+++ b/net/rxrpc/ar-accept.c
@@ -185,7 +185,7 @@ invalid_service:
        read_unlock_bh(&local->services_lock);
 
        read_lock_bh(&call->state_lock);
-       if (!test_bit(RXRPC_CALL_RELEASE, &call->flags) &&
+       if (!test_bit(RXRPC_CALL_RELEASED, &call->flags) &&
            !test_and_set_bit(RXRPC_CALL_RELEASE, &call->events)) {
                rxrpc_get_call(call);
                rxrpc_queue_call(call);