From: Christoph Hellwig <hch@lst.de>
To: 许春光 <brookxu.cn@gmail.com>
Cc: Christoph Hellwig <hch@lst.de>,
kbusch@kernel.org, axboe@kernel.dk, sagi@grimberg.me,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] nvme-core: auto add the new ns while UUID changed
Date: Mon, 18 Nov 2024 07:26:27 +0100 [thread overview]
Message-ID: <20241118062627.GA32372@lst.de> (raw)
In-Reply-To: <CADtkEec84+ECj_s4Seue5uC+xv3dBu6T4kaqeHMe9PLiLV6tUw@mail.gmail.com>
On Sat, Nov 16, 2024 at 08:49:12AM +0800, 许春光 wrote:
> Yes, now we have remove the old ns and log the change to dmesg, but I am
> confused why not auto add the ns with new UUID, we should treat it as a new
> ns? so that we can avoid an active controller with no ns, but actually it have
> one.
Because as far as the specification is concerned it is. The whole point of
these identifiers is that they are stable over the life time of the
namespace.
next prev parent reply other threads:[~2024-11-18 6:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 8:37 [PATCH v2] nvme-core: auto add the new ns while UUID changed brookxu.cn
2024-11-15 17:04 ` Christoph Hellwig
2024-11-16 0:49 ` 许春光
2024-11-18 6:26 ` Christoph Hellwig [this message]
2024-11-18 9:31 ` 许春光
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=20241118062627.GA32372@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=brookxu.cn@gmail.com \
--cc=kbusch@kernel.org \
--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