summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNitin U. Yewale <nyewale@redhat.com>2024-01-29 14:06:37 +0300
committerKeith Busch <kbusch@kernel.org>2024-02-01 18:44:52 +0300
commit524719b4c60dc5c5edff0cdfd715b4e2d6c16ede (patch)
treefb78b21eb7c60a1b71c0207df56c825008887f1d
parenta90ac7b348770ff3d246fac575306783de381e51 (diff)
downloadlinux-524719b4c60dc5c5edff0cdfd715b4e2d6c16ede.tar.xz
nvme-tcp: show hostnqn when connecting to tcp target
Log hostnqn when connecting to nvme target. As hostnqn could be changed, logging this information in syslog at appropriate time may help in troubleshooting. Signed-off-by: Nitin U. Yewale <nyewale@redhat.com> Reviewed-by: John Meneghini <jmeneghi@redhat.com> Reviewed-by: Sagi Grimberg <sagi@grimberg.me> Signed-off-by: Keith Busch <kbusch@kernel.org>
-rw-r--r--drivers/nvme/host/tcp.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/drivers/nvme/host/tcp.c b/drivers/nvme/host/tcp.c
index 9f8dea2e2c7d..a6d596e05602 100644
--- a/drivers/nvme/host/tcp.c
+++ b/drivers/nvme/host/tcp.c
@@ -2753,8 +2753,8 @@ static struct nvme_ctrl *nvme_tcp_create_ctrl(struct device *dev,
if (ret)
goto out_uninit_ctrl;
- dev_info(ctrl->ctrl.device, "new ctrl: NQN \"%s\", addr %pISp\n",
- nvmf_ctrl_subsysnqn(&ctrl->ctrl), &ctrl->addr);
+ dev_info(ctrl->ctrl.device, "new ctrl: NQN \"%s\", addr %pISp, hostnqn: %s\n",
+ nvmf_ctrl_subsysnqn(&ctrl->ctrl), &ctrl->addr, opts->host->nqn);
mutex_lock(&nvme_tcp_ctrl_mutex);
list_add_tail(&ctrl->list, &nvme_tcp_ctrl_list);