IB/iser: Fix memory regions possible leak
authorSagi Grimberg <sagig@mellanox.com>
Sun, 18 Jan 2015 14:51:06 +0000 (16:51 +0200)
committerRoland Dreier <roland@purestorage.com>
Tue, 17 Feb 2015 20:32:46 +0000 (12:32 -0800)
commit6606e6a2ff2710b473838b291dc533cd8fc1471f
tree1d37d500fd385ac7c627881b9254c37c3bb0d6b2
parentc6c95ef4cec680f7a10aa425a9970744b35b6489
IB/iser: Fix memory regions possible leak

When teardown process starts during live IO, we need to keep the
memory regions pool (frmr/fmr) until all in-flight tasks are properly
released, since each task may return a memory region to the pool. In
order to do this, we pass a destroy flag to iser_free_ib_conn_res to
indicate we can destroy the device and the memory regions
pool. iser_conn_release will pass it as true and also DEVICE_REMOVAL
event (we need to let the device to properly remove).

Also, Since we conditionally call iser_free_rx_descriptors,
remove the extra check on iser_conn->rx_descs.

Fixes: 5426b1711fd0 ("IB/iser: Collapse cleanup and disconnect handlers")
Reported-by: Or Gerlitz <ogerlitz@mellanox.com>
Signed-off-by: Sagi Grimberg <sagig@mellanox.com>
Signed-off-by: Roland Dreier <roland@purestorage.com>
drivers/infiniband/ulp/iser/iser_initiator.c
drivers/infiniband/ulp/iser/iser_verbs.c