From: Daniel Wagner <wagi@kernel.org>
To: Keith Busch <kbusch@kernel.org>, Christoph Hellwig <hch@lst.de>,
Sagi Grimberg <sagi@grimberg.me>,
James Smart <james.smart@broadcom.com>
Cc: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
Hannes Reinecke <hare@suse.de>,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
Daniel Wagner <wagi@kernel.org>
Subject: [PATCH v3 0/4] nvme-fc: fix blktests nvme/041
Date: Fri, 29 Aug 2025 17:37:24 +0200 [thread overview]
Message-ID: <20250829-nvme-fc-sync-v3-0-d69c87e63aee@kernel.org> (raw)
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>
next reply other threads:[~2025-08-29 15:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-29 15:37 Daniel Wagner [this message]
2025-08-29 15:37 ` [PATCH v3 1/4] nvme-fabrics: introduce ref-counting for nvmf_ctrl_options Daniel Wagner
2025-08-29 15:37 ` [PATCH v3 2/4] nvme-fc: reorganize ctrl ref-counting and cleanup code Daniel Wagner
2025-09-01 11:46 ` Dan Carpenter
2025-09-03 7:34 ` Daniel Wagner
2025-09-02 6:45 ` Hannes Reinecke
2025-08-29 15:37 ` [PATCH v3 3/4] nvme-fc: refactore nvme_fc_reconnect_or_delete Daniel Wagner
2025-09-02 6:47 ` Hannes Reinecke
2025-08-29 15:37 ` [PATCH v3 4/4] nvme-fc: wait for initial connect attempt to finish Daniel Wagner
2025-09-02 9:13 ` Hannes Reinecke
2025-09-03 7:45 ` Daniel Wagner
2025-10-27 21:43 ` [PATCH v3 0/4] nvme-fc: fix blktests nvme/041 Justin Tee
2025-11-06 18:41 ` Justin Tee
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250829-nvme-fc-sync-v3-0-d69c87e63aee@kernel.org \
--to=wagi@kernel.org \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=james.smart@broadcom.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=shinichiro.kawasaki@wdc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®