Another attempt to get the nvme/041 fixed. I've decided to make the
synchronous connect an opt-in feature, so that we don't break existing
users. I need to do some changes for libnvme and nvme-cli so all works
fine when users update either the userspace or kernel.

Signed-off-by: Daniel Wagner <wagi@kernel.org>
---
v3:
 - rebased to current master
 - use explicit initial connect flag to distiguish between retry and
   initial connect. Necessary to keep nvme/061 working.
 - added 'nvme-fc: refactore nvme_fc_reconnect_or_delete'
 - updated commit messages

v2:
 - renamed flag to connect_async, default false
 - add info to commit message why nvme-fc is different
 - merged connect_async with 'nvme-fc: wait for
   initial connect attempt to finish'
 - https://lore.kernel.org/all/20240221132404.6311-1-dwagner@suse.de/

v1:
 - renamed 'nvme-fc: redesign locking and refcounting'
   to 'nvme-fc: reorder ctrl ref counting and cleanup code path'
 - testing with scsi/nvme dev_loss_tmo on real hw
 - removed rport ref counting part
 - collected RB tags
 - https://lore.kernel.org/linux-nvme/20240219131531.15134-1-dwagner@suse.de/

v0:
 - initial version
 - https://lore.kernel.org/linux-nvme/20240216084526.14133-1-dwagner@suse.de/

---
Daniel Wagner (4):
      nvme-fabrics: introduce ref-counting for nvmf_ctrl_options
      nvme-fc: reorganize ctrl ref-counting and cleanup code
      nvme-fc: refactore nvme_fc_reconnect_or_delete
      nvme-fc: wait for initial connect attempt to finish

 drivers/nvme/host/fabrics.c |  40 ++++++++-
 drivers/nvme/host/fabrics.h |   9 +-
 drivers/nvme/host/fc.c      | 212 ++++++++++++++++++++++----------------------
 drivers/nvme/host/rdma.c    |  18 ++--
 drivers/nvme/host/tcp.c     |  21 +++--
 drivers/nvme/target/loop.c  |  19 ++--
 6 files changed, 192 insertions(+), 127 deletions(-)
---
base-commit: c17b750b3ad9f45f2b6f7e6f7f4679844244f0b9
change-id: 20250828-nvme-fc-sync-bbc73a36255d

Best regards,
-- 
Daniel Wagner <wagi@kernel.org>