rds: tcp: canonical connection order for all paths with index > 0
authorSowmini Varadhan <sowmini.varadhan@oracle.com>
Fri, 31 Mar 2017 22:56:31 +0000 (15:56 -0700)
committerDavid S. Miller <davem@davemloft.net>
Mon, 3 Apr 2017 02:41:00 +0000 (19:41 -0700)
commit087d975353d0cc9b7536d6ef46cd9303fceb2e17
treea8e64d94e8f4452c60969b63c6471ffd219d42c0
parente97656d03ca0cea888a0b9d382abce8233771f31
rds: tcp: canonical connection order for all paths with index > 0

The rds_connect_worker() has a bug in the check that enforces the
canonical connection order described in the comments of
rds_tcp_state_change(). The intention is to make sure that all
the multipath connections are always initiated by the smaller IP
address via rds_start_mprds. To achieve this, rds_connection_worker
should check that cp_index > 0.

Signed-off-by: Sowmini Varadhan <sowmini.varadhan@oracle.com>
Acked-by: Santosh Shilimkar <santosh.shilimkar@oracle.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
net/rds/threads.c