nvme-tcp: handle number of queue changes
Bugzilla: http://bugzilla.redhat.com/2112025
Upstream Status: From upstream git://git.infradead.org/nvme.git branch "nvme-6.1"
On reconnect, the number of queues might have changed.
In the case where we have more queues available than previously we try to access queues which are not initialized yet.
The other case where we have less queues than previously, the connection attempt will fail because the target doesn't support the old number of queues and we end up in a reconnect loop.
Thus, only start queues which are currently present in the tagset limited by the number of available queues. Then we update the tagset and we can start any new queue.
Signed-off-by: John Meneghini jmeneghi@redhat.com