linux-kernel - Re: [PATCH v2] nvme-core: auto add the new ns while UUID changed

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CADtkEefQoDY5k5_V4QEGVD+DD2iTjMLWj8KXO+PnuVT+0wHsjA@mail.gmail.com>
Date: Mon, 18 Nov 2024 17:31:49 +0800
From: 许春光 <brookxu.cn@...il.com>
To: Christoph Hellwig <hch@....de>
Cc: kbusch@...nel.org, axboe@...nel.dk, sagi@...mberg.me, 
	linux-nvme@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] nvme-core: auto add the new ns while UUID changed

Christoph Hellwig <hch@....de> 于2024年11月18日周一 14:26写道：
>
> 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.
Noted, Thanks very much~