rxrpc: Fix checks as to whether we should set up a new call
authorDavid Howells <dhowells@redhat.com>
Thu, 27 Sep 2018 14:13:08 +0000 (15:13 +0100)
committerDavid Howells <dhowells@redhat.com>
Fri, 28 Sep 2018 09:31:20 +0000 (10:31 +0100)
commitdc71db34e4f3c06b8277c8f3c2ff014610607a8c
tree24c55206f233ae13f999d814ee206d0d3842e936
parent092ffc51fb3f9b8369e737c9320bf0bffb2c898f
rxrpc: Fix checks as to whether we should set up a new call

There's a check in rxrpc_data_ready() that's checking the CLIENT_INITIATED
flag in the packet type field rather than in the packet flags field.

Fix this by creating a pair of helper functions to check whether the packet
is going to the client or to the server and use them generally.

Fixes: 248f219cb8bc ("rxrpc: Rewrite the data and ack handling code")
Signed-off-by: David Howells <dhowells@redhat.com>
net/rxrpc/ar-internal.h
net/rxrpc/conn_object.c
net/rxrpc/input.c