public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Keith Busch <kbusch@kernel.org>
To: Hannes Reinecke <hare@suse.de>
Cc: Keith Busch <kbusch@meta.com>,
	linux-nvme@lists.infradead.org, hch@lst.de, mlombard@redhat.com,
	jmeneghi@redhat.com
Subject: Re: [RFC-PATCH 2/2] nvme: use the namespace id for block device names
Date: Tue, 3 Mar 2026 08:39:56 -0700	[thread overview]
Message-ID: <aacAzGpNJ2RXedvG@kbusch-mbp> (raw)
In-Reply-To: <c2ef8067-a5c9-4be7-8e2a-9d74610d446f@suse.de>

On Tue, Mar 03, 2026 at 08:34:38AM +0100, Hannes Reinecke wrote:
> The idea is nice, and I would love to go into that
> direction.
> But have you checked how this holds up under
> rescan/remapping (eg things like blktest/nvme/058)?
> Removal of the sysfs nodes might be delayed, and we cannot
> create new entries with the same name until then.
> So if that is taken care of, fine, but I don't see that in
> the patch ...

I see. I set out to ensure everything was ordered, but apparently I've
missed this case. Thanks for pointing out the test.


  reply	other threads:[~2026-03-03 15:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-02 22:25 [RFC-PATCH 1/2] nvme-multipath: delete gendisk under subsys lock Keith Busch
2026-03-02 22:25 ` [RFC-PATCH 2/2] nvme: use the namespace id for block device names Keith Busch
2026-03-03  7:34   ` Hannes Reinecke
2026-03-03 15:39     ` Keith Busch [this message]
2026-03-03 16:53       ` Keith Busch
2026-03-04 11:55         ` Nilay Shroff
2026-03-04 14:53           ` Keith Busch
2026-03-03  7:29 ` [RFC-PATCH 1/2] nvme-multipath: delete gendisk under subsys lock Hannes Reinecke

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