rds/rdma: correctly assign the dest qp num in rds ib connection

Commit 7622b0c ("net/rds: Extract dest qp num for displaying in
rds-info") assigns the dest qp num in rds ib connection during
RDMA_CM_EVENT_ESTABLISHED event handling. This works good for active
side of the connection. For passive side, the dest qp num is passed in
the RDMA_CM_EVENT_CONNECT_REQUEST event. This patch adds the change that
sets dest qp num in rds ib connection during
RDMA_CM_EVENT_CONNECT_REQUEST event handling.

Without this patch, the dest qp num on passive side is set to 0. We can
observe this behavior in rds-info -I output.

Fixes: 7622b0c ("net/rds: Extract dest qp num for displaying in
rds-info")

v1->v2: Addressed review comments on where to set dest qp num.

Orabug: 34429478
Signed-off-by: Rohit Nair <[email protected]>
Reviewed-by: Arumugam Kolappan <[email protected]>
Signed-off-by: Saeed Mirzamohammadi <[email protected]>

Author: RN97

net/rds/ib_cm.c

@@ -394,7 +394,8 @@ void rds_ib_cm_connect_complete(struct rds_connection *conn, struct rdma_cm_even
 
 	/* Save the qp number information in the connection details. */
 	ic->i_qp_num = ic->i_cm_id->qp->qp_num;
-	ic->i_dst_qp_num = event->param.conn.qp_num;
+	if (event->param.conn.qp_num)
+		ic->i_dst_qp_num = event->param.conn.qp_num;
 
 	rds_ib_cancel_cm_watchdog(ic, "connect complete");
 
@@ -1642,6 +1643,8 @@ int rds_ib_cm_handle_connect(struct rdma_cm_id *cm_id,
 				       event->param.conn.initiator_depth);
 		if (err)
 			reason = "rds_ib_cm_accept failed";
+		else if (event->param.conn.qp_num)
+			ic->i_dst_qp_num = event->param.conn.qp_num;
 	}
 
 out: