[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 07:51:32 +0200 |
On Apr 20 07:33, Christoph Hellwig wrote:
> On Tue, Apr 19, 2022 at 02:10:38PM +0200, Klaus Jensen wrote:
> > From: Klaus Jensen <k.jensen@samsung.com>
> >
> > Do not default to generate an UUID for namespaces if it is not
> > explicitly specified.
> >
> > This is a technically a breaking change in behavior. However, since the
> > UUID changes on every VM launch, it is not spec compliant and is of
> > little use since the UUID cannot be used reliably anyway and the
> > behavior prior to this patch must be considered buggy.
>
> 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.
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