[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <C8AA0F1E-6299-49CA-B470-6E95CD1FA081@javigon.com>
Date: Thu, 24 Jan 2019 17:41:18 +0100
From: Javier González <javier@...igon.com>
To: Andy Shevchenko <andy.shevchenko@...il.com>
Cc: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Christoph Hellwig <hch@....de>,
Matias Bjørling <mb@...htnvm.io>,
linux-block@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v1] : Switch to use new generic UUID API
> On 24 Jan 2019, at 17.38, Andy Shevchenko <andy.shevchenko@...il.com> wrote:
>
> On Thu, Jan 24, 2019 at 4:36 PM Javier González <javier@...igon.com> wrote:
>
>> It is not pushed anywhere yet, but I have been working on a tool to make
>> a pblk recovery tool to enable FTL repairs if something fails in the
>> kernel recovery path. Here, I use this uuid to identify the
>> instance - is there a way to reconcile guid_t with user space, which
>> currently uses the __u8?
>
> For Linux there is util-linux which contains libuuid. There is uuid_t type.
> Unfortunately there is no so called LE (little endian) variant.
> Perhaps someone would need to extend the support for that.
Ok. I can look into that when releasing pblk-tools. But for now, I am OK
with applying with the changes Christoph suggested and aligning with
guid_t if you also think helps maintaining common helpers.
Javier
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists