Re: [PATCH 1/1] iser-target: Fix handling of RDMA_CV_EVENT_ADDR_CHANGE
From: Jason Gunthorpe <jgg@nvidia.com>
Date: 2021-07-19 12:13:06
On Wed, Jul 14, 2021 at 09:26:46PM +0300, lanevdenoche@gmail.com wrote:
quoted hunk ↗ jump to hunk
@@ -2466,6 +2489,8 @@ isert_free_np(struct iscsi_np *np) } mutex_unlock(&isert_np->mutex); + destroy_workqueue(isert_np->reinit_id_wq); +
This is racy, the lines above have: if (isert_np->cm_id) rdma_destroy_id(isert_np->cm_id); And I don't see anything preventing that from running concurrently with the WQ What is this trying to do anyhow? If the addr has truely changed why does the bind fail? Jason