net/rds: Fixing INIT2RTR_QP(0x503), syndrome (0x1796e4) (IB_AH_GRH present) issue.

Fixing the "mlx5_core 0000:b0:00.0: mlx5_cmd_check:701:(pid 3104): INIT2RTR_QP(0x503) op_mod(0x0) failed, status bad parameter(0x3), syndrome (0x1796e4)" issue.
Found this via "google"
https://gist.github.com/lukego/8b4e567f4d5c4b60da6545e063888391
BAD_PARAM | 0x1796E4 | address_path.grh is IB native connected only field

Orabug: 27383162
Orabug: 27364391

Merge-Monkey-Notes:
  This is a temporary workaround. The real fix is currently being worked on.
Merge-Monkey: Gerd Rausch <[email protected]>

Signed-off-by: Gerd Rausch <[email protected]>

Reviewed-by: Sudhakar Dindukurti <[email protected]>
Signed-off-by: Somasundaram Krishnasamy <[email protected]>

Author: Wei Lin Guay

net/rds/ib_cm.c

@@ -1573,7 +1573,6 @@ int rds_ib_setup_fastreg(struct rds_ib_device *rds_ibdev)
 	qp_attr.path_mtu	= IB_MTU_256;
 	qp_attr.dest_qp_num	= rds_ibdev->fastreg_qp->qp_num;
 	qp_attr.rq_psn		= 1;
-	qp_attr.ah_attr.ah_flags	= IB_AH_GRH;
 	qp_attr.ah_attr.ib.dlid		= port_attr.lid;
 	qp_attr.ah_attr.ib.src_path_bits	= 0;
 	qp_attr.ah_attr.sl		= 0;