Skip to contentSkip to conversation

nvme-rdma: don't use IB-CM status code in reject path

PATCH New Steve Wise 2 participants 2 messages Jun 13, 2016 – Jun 15, 2016

Subsystems (2)
lore
Share & tools
lore

Steve Wise

author
#0 lore raw

PATCH 1/1 nvme-rdma: don't use IB-CM status code in reject path

Instead, check the private data length to determine if there is private data in the reject.

Signed-off-by Steve Wise <swise at opengridcomputing.com>
---
 drivers/nvme/host/rdma.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/nvme/host/rdma.c +1 -1
index 7506431..e1205c0 100644
@@ -1208,7 +1208,7 @@ out_destroy_queue_ib:
 static int nvme_rdma_conn_rejected(struct nvme_rdma_queue *queue,
 		struct rdma_cm_event *ev)
 {
-	if (ev->status == IB_CM_REJ_CONSUMER_DEFINED) {
+	if (ev->param.conn.private_data_len) {
 		struct nvme_rdma_cm_rej *rej =
 			(struct nvme_rdma_cm_rej *)ev->param.conn.private_data;
 
Signature · 1 line
2.7.0
maintainer Applied
#1 lore raw

PATCH 1/1 nvme-rdma: don't use IB-CM status code in reject path

Quoted 4 lines · Steve Wise

Instead, check the private data length to determine if there is private data in the reject.

Signed-off-by Steve Wise <swise at opengridcomputing.com>

Thanks Steve,

applied.