Patch "nvme-fabrics: show well known discovery name" has been added to the 6.1-stable tree

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



This is a note to let you know that I've just added the patch titled

    nvme-fabrics: show well known discovery name

to the 6.1-stable tree which can be found at:
    http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
     nvme-fabrics-show-well-known-discovery-name.patch
and it can be found in the queue-6.1 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@xxxxxxxxxxxxxxx> know about it.



commit e99d78f3d32b9609ac80f6e83eca5dcaea52de9b
Author: Daniel Wagner <dwagner@xxxxxxx>
Date:   Tue Feb 21 17:51:06 2023 +0100

    nvme-fabrics: show well known discovery name
    
    [ Upstream commit 26a57cb35548ae67c14871cccbf50da3edb01ea4 ]
    
    The kernel always logs the unique subsystem name for a discovery
    controller, even in the case user space asked for the well known.
    
    This has lead to confusion as the logs of nvme-cli and the kernel
    logs didn't match.
    
    First, nvme-cli connects to the well known discovery controller to
    figure out if it supports TP8013. If so then nvme-cli disconnects and
    connects to the unique discovery controller. Currently, the kernel show
    that user space connected twice to the unique one.
    
    To avoid further confusion, show the well known discovery controller if
    user space asked for it:
    
      $ nvme connect-all -v -t tcp -a 192.168.0.1
      nvme0: nqn.2014-08.org.nvmexpress.discovery connected
      nvme0: nqn.2014-08.org.nvmexpress.discovery disconnected
      nvme0: nqn.discovery connected
    
      kernel log:
      nvme nvme0: new ctrl: NQN "nqn.2014-08.org.nvmexpress.discovery", addr 192.168.0.1:8009
      nvme nvme0: Removing ctrl: NQN "nqn.2014-08.org.nvmexpress.discovery"
      nvme nvme0: new ctrl: NQN "nqn.discovery", addr 192.168.0.1:8009
    
    Fixes: e5ea42faa773 ("nvme: display correct subsystem NQN")
    Signed-off-by: Daniel Wagner <dwagner@xxxxxxx>
    Reviewed-by: Hannes Reinecke <hare@xxxxxxx>
    Signed-off-by: Christoph Hellwig <hch@xxxxxx>
    Signed-off-by: Sasha Levin <sashal@xxxxxxxxxx>

diff --git a/drivers/nvme/host/fabrics.h b/drivers/nvme/host/fabrics.h
index a6e22116e1396..dcac3df8a5f76 100644
--- a/drivers/nvme/host/fabrics.h
+++ b/drivers/nvme/host/fabrics.h
@@ -189,7 +189,8 @@ nvmf_ctlr_matches_baseopts(struct nvme_ctrl *ctrl,
 
 static inline char *nvmf_ctrl_subsysnqn(struct nvme_ctrl *ctrl)
 {
-	if (!ctrl->subsys)
+	if (!ctrl->subsys ||
+	    !strcmp(ctrl->opts->subsysnqn, NVME_DISC_SUBSYS_NAME))
 		return ctrl->opts->subsysnqn;
 	return ctrl->subsys->subnqn;
 }



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux