From mboxrd@z Thu Jan  1 00:00:00 1970
From: hch@lst.de ('Christoph Hellwig')
Date: Mon, 7 Nov 2016 19:41:26 +0100
Subject: nvmet_rdma crash - DISCONNECT event with NULL queue
In-Reply-To: <1478543378.3350.17.camel@linux.intel.com>
References: <01d101d2345e$2f054390$8d0fcab0$@opengridcomputing.com>
 <dbe5f18d-7928-f065-920f-753b30fb99a2@grimberg.me>
 <01d901d2345f$da0d2e00$8e278a00$@opengridcomputing.com>
 <1d09c064-1cbe-7e6e-43d2-cfa6cf0c19ea@grimberg.me>
 <024e01d23476$6668b890$333a29b0$@opengridcomputing.com>
 <3512b8bb-4d29-b90a-49e1-ebf1085c47d7@grimberg.me>
 <004601d2351a$d9db85b0$8d929110$@opengridcomputing.com>
 <20161102151540.GB14825@lst.de>
 <bd82c206-668a-0794-2d51-3c48058350d3@grimberg.me>
 <1478543378.3350.17.camel@linux.intel.com>
Message-ID: <20161107184126.GA4400@lst.de>

On Mon, Nov 07, 2016@10:29:38AM -0800, J Freyensee wrote:
> The way I interpret the spec, ctrlid (I'm assuming you mean cntlid) is
> allocated on a NVM subsystem basis. ?For example, Figure 34 of the
> Discovery Log Page entry and Figure 20 of the Connect Command implies
> to me CNTLID values are allocated on a NVM Subsystem granular-level
> when I see statements such as:

It is per-subsystem.  But nothing in the spec prohibits and implementation
that has multiple subsystems to simply not allocate cntlids that
would conflict betweens it's subsystems.

And in fact there is a TP in the working group that would require
implementations not to reuse cntlids for it to work.  We'll probably
hear more about that once it's published.