Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Max Gurtovoy <mgurtovoy@nvidia.com>,
	oren@nvidia.com, linux-nvme@lists.infradead.org,
	sagi@grimberg.me, kbusch@kernel.org, hch@lst.de,
	chaitanya.kulkarni@wdc.com
Cc: israelr@nvidia.com, nitzanc@nvidia.com
Subject: Re: [PATCH 1/1] nvme: update enumerations for status codes
Date: Thu, 14 Jan 2021 12:12:53 +0100	[thread overview]
Message-ID: <a6251b7c-e2aa-7967-2e20-2983905818a8@suse.de> (raw)
In-Reply-To: <20210104125947.160984-1-mgurtovoy@nvidia.com>

On 1/4/21 1:59 PM, Max Gurtovoy wrote:
> All the updates are mentioned in the ratified NVMe 1.4 spec.
> 
> Signed-off-by: Max Gurtovoy <mgurtovoy@nvidia.com>
> ---
>   include/linux/nvme.h | 24 ++++++++++++++++++++----
>   1 file changed, 20 insertions(+), 4 deletions(-)
> 
> diff --git a/include/linux/nvme.h b/include/linux/nvme.h
> index d92535997687..1c9c34be8194 100644
> --- a/include/linux/nvme.h
> +++ b/include/linux/nvme.h
> @@ -1467,20 +1467,29 @@ enum {
>   	NVME_SC_SGL_INVALID_DATA	= 0xf,
>   	NVME_SC_SGL_INVALID_METADATA	= 0x10,
>   	NVME_SC_SGL_INVALID_TYPE	= 0x11,
> -
> +	NVME_SC_CMB_INVALID_USE		= 0x12,
> +	NVME_SC_PRP_INVALID_OFFSET	= 0x13,
> +	NVME_SC_ATOMIC_WU_EXCEEDED	= 0x14,
> +	NVME_SC_OP_DENIED		= 0x15,
>   	NVME_SC_SGL_INVALID_OFFSET	= 0x16,
> -	NVME_SC_SGL_INVALID_SUBTYPE	= 0x17,
> -
> +	NVME_SC_RESERVED		= 0x17,
> +	NVME_SC_HOST_ID_INCONSIST	= 0x18,
> +	NVME_SC_KA_TIMEOUT_EXPIRED	= 0x19,
> +	NVME_SC_KA_TIMEOUT_INVALID	= 0x1A,
> +	NVME_SC_ABORTED_PREEMPT_ABORT	= 0x1B,
>   	NVME_SC_SANITIZE_FAILED		= 0x1C,
>   	NVME_SC_SANITIZE_IN_PROGRESS	= 0x1D,
> -
> +	NVME_SC_SGL_INVALID_GRANULARITY	= 0x1E,
> +	NVME_SC_CMD_NOT_SUP_CMB_QUEUE	= 0x1F,
>   	NVME_SC_NS_WRITE_PROTECTED	= 0x20,
>   	NVME_SC_CMD_INTERRUPTED		= 0x21,
> +	NVME_SC_TRANSIENT_TR_ERR	= 0x22,
>   
>   	NVME_SC_LBA_RANGE		= 0x80,
>   	NVME_SC_CAP_EXCEEDED		= 0x81,
>   	NVME_SC_NS_NOT_READY		= 0x82,
>   	NVME_SC_RESERVATION_CONFLICT	= 0x83,
> +	NVME_SC_FORMAT_IN_PROGRESS	= 0x84,
>   
>   	/*
>   	 * Command Specific Status:
> @@ -1513,8 +1522,15 @@ enum {
>   	NVME_SC_NS_NOT_ATTACHED		= 0x11a,
>   	NVME_SC_THIN_PROV_NOT_SUPP	= 0x11b,
>   	NVME_SC_CTRL_LIST_INVALID	= 0x11c,
> +	NVME_SC_SELT_TEST_IN_PROGRESS	= 0x11d,
>   	NVME_SC_BP_WRITE_PROHIBITED	= 0x11e,
> +	NVME_SC_CTRL_ID_INVALID		= 0x11f,
> +	NVME_SC_SEC_CTRL_STATE_INVALID	= 0x120,
> +	NVME_SC_CTRL_RES_NUM_INVALID	= 0x121,
> +	NVME_SC_RES_ID_INVALID		= 0x122,
>   	NVME_SC_PMR_SAN_PROHIBITED	= 0x123,
> +	NVME_SC_ANA_GROUP_ID_INVALID	= 0x124,
> +	NVME_SC_ANA_ATTACH_FAILED	= 0x125,
>   
>   	/*
>   	 * I/O Command Set Specific - NVM commands:
> 
Reviewed-by: Hannes Reinecke <hare@suse.de>

Cheers,

Hannes
-- 
Dr. Hannes Reinecke                Kernel Storage Architect
hare@suse.de                              +49 911 74053 688
SUSE Software Solutions GmbH, Maxfeldstr. 5, 90409 Nürnberg
HRB 36809 (AG Nürnberg), Geschäftsführer: Felix Imendörffer

_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

  reply	other threads:[~2021-01-14 11:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-04 12:59 [PATCH 1/1] nvme: update enumerations for status codes Max Gurtovoy
2021-01-14 11:12 ` Hannes Reinecke [this message]
2021-01-14 17:52 ` Christoph Hellwig
2021-01-19 14:20   ` Max Gurtovoy
2021-01-20  5:09 ` Chaitanya Kulkarni
2021-01-20 10:02   ` Max Gurtovoy
2021-01-21  8:08     ` Chaitanya Kulkarni

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=a6251b7c-e2aa-7967-2e20-2983905818a8@suse.de \
    --to=hare@suse.de \
    --cc=chaitanya.kulkarni@wdc.com \
    --cc=hch@lst.de \
    --cc=israelr@nvidia.com \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=mgurtovoy@nvidia.com \
    --cc=nitzanc@nvidia.com \
    --cc=oren@nvidia.com \
    --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