Skip to content

nvme: fix stuck discovery

Hannes Reinecke linux-nvme 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest3 patches 0 repliesNew

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/3nvme: centralize discovery controller defaultsdrivers/nvme/host/fabrics.c+4 -42 replies
2/3nvme: avoid reconnection for the discovery controllerdrivers/nvme/host/fabrics.c+3 -01 reply
2/3nvme: avoid reconnection for the discovery controller+0 -00 replies
3/3nvme: allow duplicate connections to the discovery controllerdrivers/nvme/host/core.c drivers/nvme/host/fabrics.c+3 -13 replies
3/3nvme: allow duplicate connections to the discovery controller+0 -01 reply
3/3nvme: allow duplicate connections to the discovery controller+0 -00 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/3] nvme: fix stuck discovery

Hi all,

when the user manages to abort a 'nvme discover' the resulting discovery controller is never removed, as it will try to reconnect for ever. And as the 'duplicate_connect' option is not given any further attempt will be returned with -EALREADY.

This patchset fixes this issue by a) disabling reconnection attempts and b) allowing for duplicate connections on the discovery controller.

As usual, comments and reviews are welcome.

Hannes Reinecke (3):
nvme: centralize discovery controller defaults
nvme: avoid reconnection for the discovery controller
nvme: allow duplicate connections to the discovery controller

 drivers/nvme/host/core.c    |  3 ++-
 drivers/nvme/host/fabrics.c | 12 ++++++++----
 2 files changed, 10 insertions(+), 5 deletions(-)
Signature · 1 line
2.12.3