public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Max Gurtovoy <mgurtovoy@nvidia.com>
To: <hch@lst.de>, <linux-nvme@lists.infradead.org>,
	<sagi@grimberg.me>, <kbusch@kernel.org>, <kch@nvidia.com>
Cc: Max Gurtovoy <mgurtovoy@nvidia.com>
Subject: [PATCH 2/2] nvme: add missing status values to verbose logging
Date: Thu, 28 Apr 2022 12:19:35 +0300	[thread overview]
Message-ID: <20220428091935.35651-2-mgurtovoy@nvidia.com> (raw)
In-Reply-To: <20220428091935.35651-1-mgurtovoy@nvidia.com>

The following status values were added: NVME_SC_INTERNAL_PATH_ERROR,
NVME_SC_CTRL_PATH_ERROR and NVME_SC_HOST_ABORTED_CMD.

Signed-off-by: Max Gurtovoy <mgurtovoy@nvidia.com>
---
 drivers/nvme/host/constants.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/drivers/nvme/host/constants.c b/drivers/nvme/host/constants.c
index 6c2aa8eefb55..1dd1d78de295 100644
--- a/drivers/nvme/host/constants.c
+++ b/drivers/nvme/host/constants.c
@@ -154,10 +154,13 @@ static const char * const nvme_statuses[] = {
 	[NVME_SC_COMPARE_FAILED] = "Compare Failure",
 	[NVME_SC_ACCESS_DENIED] = "Access Denied",
 	[NVME_SC_UNWRITTEN_BLOCK] = "Deallocated or Unwritten Logical Block",
+	[NVME_SC_INTERNAL_PATH_ERROR] = "Internal Pathing Error",
 	[NVME_SC_ANA_PERSISTENT_LOSS] = "Asymmetric Access Persistent Loss",
 	[NVME_SC_ANA_INACCESSIBLE] = "Asymmetric Access Inaccessible",
 	[NVME_SC_ANA_TRANSITION] = "Asymmetric Access Transition",
+	[NVME_SC_CTRL_PATH_ERROR] = "Controller Pathing Error",
 	[NVME_SC_HOST_PATH_ERROR] = "Host Pathing Error",
+	[NVME_SC_HOST_ABORTED_CMD] = "Host Aborted Command",
 };
 
 const unsigned char *nvme_get_error_status_str(u16 status)
-- 
2.18.2



  reply	other threads:[~2022-04-28  9:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-28  9:19 [PATCH 1/2] nvme: add missing path related status values Max Gurtovoy
2022-04-28  9:19 ` Max Gurtovoy [this message]
2022-04-29  6:08   ` [PATCH 2/2] nvme: add missing status values to verbose logging Hannes Reinecke
2022-05-01  8:24     ` Max Gurtovoy
2022-04-29  6:08 ` [PATCH 1/2] nvme: add missing path related status values Hannes Reinecke
2022-05-10  6:19 ` Christoph Hellwig

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=20220428091935.35651-2-mgurtovoy@nvidia.com \
    --to=mgurtovoy@nvidia.com \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=kch@nvidia.com \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /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