summaryrefslogtreecommitdiffstats
path: root/drivers/message
diff options
context:
space:
mode:
authorSagi Grimberg <sagi@grimberg.me>2016-07-14 16:39:47 +0200
committerSagi Grimberg <sagi@grimberg.me>2016-08-03 15:25:07 +0200
commit57de5a0a40db97bb390d3ac1f4c2e74b9f3515c3 (patch)
tree698913355a30c7e313c1347064c565dbf55516b5 /drivers/message
parentnvme-rdma: Queue ns scanning after a sucessful reconnection (diff)
downloadlinux-57de5a0a40db97bb390d3ac1f4c2e74b9f3515c3.tar.xz
linux-57de5a0a40db97bb390d3ac1f4c2e74b9f3515c3.zip
nvme-rdma: Fix device removal handling
Device removal sequence may have crashed because the controller (and admin queue space) was freed before we destroyed the admin queue resources. Thus we want to destroy the admin queue and only then queue controller deletion and wait for it to complete. More specifically we: 1. own the controller deletion (make sure we are not competing with another deletion). 2. get rid of inflight reconnects if exists (which also destroy and create queues). 3. destroy the queue. 4. safely queue controller deletion (and wait for it to complete). Reported-by: Steve Wise <swise@opengridcomputing.com> Signed-off-by: Sagi Grimberg <sagi@grimberg.me> Reviewed-by: Christoph Hellwig <hch@lst.de>
Diffstat (limited to 'drivers/message')
0 files changed, 0 insertions, 0 deletions