From: Johannes Thumshirn <jthumshirn@suse.de>
Date: Thu, 19 Apr 2018 17:43:42 +0000 (+0200)
Subject: nvme: fc: provide a descriptive error
X-Git-Tag: v4.18-rc1~192^2~88^2~14
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=4fb135ad154060bf289ccf35734e3d3b6e5029a7;p=thirdparty%2Fkernel%2Flinux.git

nvme: fc: provide a descriptive error

Provide a descriptive error in case an lport to rport association
isn't found when creating the FC-NVME controller.

Currently it's very hard to debug the reason for a failed connect
attempt without a look at the source.

Signed-off-by: Johannes Thumshirn <jthumshirn@suse.de>
Reviewed-by: James Smart  <james.smart@broadcom.com>
Reviewed-by: Hannes Reinecke <hare@suse.com>
Signed-off-by: Keith Busch <keith.busch@intel.com>
---

diff --git a/drivers/nvme/host/fc.c b/drivers/nvme/host/fc.c
index 6cb26bcf6ec01..8b66879b4ebf8 100644
--- a/drivers/nvme/host/fc.c
+++ b/drivers/nvme/host/fc.c
@@ -3284,6 +3284,8 @@ nvme_fc_create_ctrl(struct device *dev, struct nvmf_ctrl_options *opts)
 	}
 	spin_unlock_irqrestore(&nvme_fc_lock, flags);
 
+	pr_warn("%s: %s - %s combination not found\n",
+		__func__, opts->traddr, opts->host_traddr);
 	return ERR_PTR(-ENOENT);
 }