Thread (8 messages) 8 messages, 3 authors, 2016-08-02
STALE3620d

Re: [PATCH v3] nvmet-rdma: Correctly handle RDMA device hot removal

From: Bart Van Assche <hidden>
Date: 2016-08-01 14:44:37
Also in: linux-nvme

On 08/01/16 04:15, Christoph Hellwig wrote:
This looks reasonable to me, but a little question below:
quoted
@@ -1442,7 +1491,8 @@ static void nvmet_rdma_remove_port(struct nvmet_port *port)
 {
 	struct rdma_cm_id *cm_id = port->priv;

-	rdma_destroy_id(cm_id);
+	if (cm_id)
+		rdma_destroy_id(cm_id);
 }
How is ->remove_port synchronized vs the RDMA/CM event handler?
rdma_destroy_id() waits until active RDMA/CM callbacks have finished. Is 
that sufficient or is further synchronization needed?

Bart.

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help