rxrpc: When clearing a socket, clear the call sets in the right order
authorDavid Howells <dhowells@redhat.com>
Tue, 23 Aug 2016 14:27:24 +0000 (15:27 +0100)
committerDavid Howells <dhowells@redhat.com>
Tue, 23 Aug 2016 14:27:24 +0000 (15:27 +0100)
commitf36b5e444cf772f52782d47e99c68fef20ac5195
tree0601bb884f49ff91e64775bf6502aea3bb1bde1b
parentdabe5a790655c79f47d75749874ce7b4d5016de9
rxrpc: When clearing a socket, clear the call sets in the right order

When clearing a socket, we should clear the securing-in-progress list
first, then the accept queue and last the main call tree because that's the
order in which a call progresses.  Not that a call should move from the
accept queue to the main tree whilst we're shutting down a socket, but it a
call could possibly move from sequreq to acceptq whilst we're clearing up.

Signed-off-by: David Howells <dhowells@redhat.com>
net/rxrpc/call_object.c