nvme/rdma initiator stuck on reboot

[Steve Wise]

> 
> >> Can this be related due to the fact that we use a signle-threaded
> >> workqueue for delete/reset/reconnect? (delete cancel_sync the active
> >> reconnect work...)
> >>
> >> Does this untested patch help?
> >
> > That seems to do it!
> 
> Is this a formal tested-by?

Sure, but let me ask a question:  So the bug was that the delete controller
worker was blocked waiting for the reconnect worker to complete.  Yes?  And the
reconnect worker was never completing?  Why is that?  Here are a few tidbits
about iWARP connections:  address resolution == neighbor discovery.  So if the
neighbor is unreachable, it will take a few seconds for the OS to give up and
fail the resolution.  If the neigh entry is valid and the peer becomes
unreachable during connection setup, it might take 60 seconds or so for a
connect operation to give up and fail.  So this is probably slowing the
reconnect thread down.   But shouldn't the reconnect thread notice that a delete
is trying to happen and bail out?