[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 4/5] hw/nvme: do not auto-generate uuid
From: |
Klaus Jensen |
Subject: |
Re: [PATCH 4/5] hw/nvme: do not auto-generate uuid |
Date: |
Wed, 20 Apr 2022 08:58:26 +0200 |
On Apr 20 08:53, Christoph Hellwig wrote:
> On Wed, Apr 20, 2022 at 07:51:32AM +0200, Klaus Jensen wrote:
> > > So unlike the EUI, UUIDs are designed to be autogenerated even if the
> > > current algorithm is completely broken. We'd just need to persist them.
> > > Note that NVMe at least in theory requires providing at least on of
> > > the unique identifiers, and the UUID is the only one designed to be
> > > autogenerated in a distributed fashion.
> >
> > I understand, but it boils down to the fact that we do not have a
> > general method of storing "metadata" like this persistently.
> >
> > But maybe it is time that we come up with something to do this.
>
> If we can't make the persistent uniqueue identifiers persistent and
> unique, we should not provide them. While NVMe does require a
> namespace to report at least one of the three identifies, the failure
> mode for now having one is much more graceful than providing one that
> is not unique or not persistent.
Alright. I think we can do that. We can revert the eui64 defaulting as
well.
Thanks for your reviews/comments Christoph.
signature.asc
Description: PGP signature
[PATCH 5/5] hw/nvme: bump firmware revision, Klaus Jensen, 2022/04/19
Re: [PATCH 0/5] hw/nvme: fix namespace identifiers, Keith Busch, 2022/04/19