Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Busch <kbusch@kernel.org>
To: Maurizio Lombardi <mlombard@redhat.com>
Cc: hch@lst.de, sagi@grimberg.me, kch@nvidia.com,
	linux-nvme@lists.infradead.org, kbusch@meta.com
Subject: Re: [PATCH V2] nvmet: Identify-Active Namespace ID List command should reject invalid nsid
Date: Fri, 30 Aug 2024 08:36:16 -0600	[thread overview]
Message-ID: <ZtHY4G9Cyqej_zfr@kbusch-mbp> (raw)
In-Reply-To: <20240829095214.48915-1-mlombard@redhat.com>

On Thu, Aug 29, 2024 at 11:52:14AM +0200, Maurizio Lombardi wrote:
> nsid values of 0xFFFFFFFE and 0XFFFFFFFF should be rejected with
> a status code of "Invalid Namespace or Format".
> See NVMe Base Specification, Active Namespace ID list (CNS 02h).

Thanks, applied to nvme-6.11.


      parent reply	other threads:[~2024-08-30 14:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-29  9:52 [PATCH V2] nvmet: Identify-Active Namespace ID List command should reject invalid nsid Maurizio Lombardi
2024-08-30 10:03 ` Sagi Grimberg
2024-08-30 14:36 ` Keith Busch [this message]

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=ZtHY4G9Cyqej_zfr@kbusch-mbp \
    --to=kbusch@kernel.org \
    --cc=hch@lst.de \
    --cc=kbusch@meta.com \
    --cc=kch@nvidia.com \
    --cc=linux-nvme@lists.infradead.org \
    --cc=mlombard@redhat.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