From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH] NVMe: Use IDA for namespace disk naming
Date: Tue, 23 Feb 2016 22:56:36 +0000 [thread overview]
Message-ID: <20160223225635.GB20250@localhost.localdomain> (raw)
In-Reply-To: <20160221161249.GA21099@infradead.org>
On Sun, Feb 21, 2016@08:12:49AM -0800, Christoph Hellwig wrote:
> On Thu, Feb 18, 2016@11:18:05AM -0700, Keith Busch wrote:
> > A namespace may be detached from a controller, but a user may be holding
> > a reference to it. Attaching a new namespace with the same NSID will create
> > duplicate names when using the NSID to name the disk.
>
> This looks sensible, but I fear we might be running into the same
> issue with the backing_device embedded in the request_queue.
I don't think I follow. On rescanning, a new namespace with the same
NSID as a previously deleted one will allocate a new request_queue.
next prev parent reply other threads:[~2016-02-23 22:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 18:18 [PATCH] NVMe: Use IDA for namespace disk naming Keith Busch
2016-02-21 16:12 ` Christoph Hellwig
2016-02-23 22:56 ` Keith Busch [this message]
2016-02-24 13:05 ` Christoph Hellwig
2016-02-24 14:58 ` Keith Busch
2016-02-24 19:33 ` Christoph Hellwig
2016-02-22 8:54 ` Sagi Grimberg
2016-02-25 8:55 ` Sagi Grimberg
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=20160223225635.GB20250@localhost.localdomain \
--to=keith.busch@intel.com \
/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