Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Busch <kbusch@kernel.org>
To: Kamaljit Singh <kamaljit.singh@opensource.wdc.com>
Cc: axboe@kernel.dk, hch@lst.de, sagi@grimberg.me,
	linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
	cassel@kernel.org, dlemoal@kernel.org, kamaljit.singh1@wdc.com
Subject: Re: [PATCH v2 0/2] Preclude IOCCSZ/IORCSZ validation for admin controller connect
Date: Wed, 17 Sep 2025 16:41:56 -0600	[thread overview]
Message-ID: <aMs5NJdx7I3WZ0rg@kbusch-mbp> (raw)
In-Reply-To: <20250905232550.1950307-1-kamaljit.singh@opensource.wdc.com>

On Fri, Sep 05, 2025 at 04:25:48PM -0700, Kamaljit Singh wrote:
> During negative testing it was observed that when ioccsz and/or iorcsz 
> were cleared to zero on a Target, a new connection to an administrative 
> controller failed to establish, due to driver validation of those fields. 
> Since an administrative controller does not support I/O queues, these 
> checks should be excluded for such a controller.

Thanks, applied to nvme-6.18.


      parent reply	other threads:[~2025-09-17 22:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-05 23:25 [PATCH v2 0/2] Preclude IOCCSZ/IORCSZ validation for admin controller connect Kamaljit Singh
2025-09-05 23:25 ` [PATCH v2 1/2] nvme-core: add method to check for an I/O controller Kamaljit Singh
2025-09-08 12:56   ` Hannes Reinecke
2025-09-17 21:42     ` Kamaljit Singh
2025-09-05 23:25 ` [PATCH v2 2/2] nvme-core: do ioccsz/iorcsz validation only for I/O controllers Kamaljit Singh
2025-09-08 12:57   ` Hannes Reinecke
2025-09-17 21:43     ` Kamaljit Singh
2025-09-17 22:41 ` 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=aMs5NJdx7I3WZ0rg@kbusch-mbp \
    --to=kbusch@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=cassel@kernel.org \
    --cc=dlemoal@kernel.org \
    --cc=hch@lst.de \
    --cc=kamaljit.singh1@wdc.com \
    --cc=kamaljit.singh@opensource.wdc.com \
    --cc=linux-kernel@vger.kernel.org \
    --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