[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1495718961.6967.117.camel@linux.intel.com>
Date: Thu, 25 May 2017 16:29:21 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Christoph Hellwig <hch@....de>
Cc: Amir Goldstein <amir73il@...il.com>, linux-fsdevel@...r.kernel.org,
Shaohua Li <shli@...nel.org>,
Dan Williams <dan.j.williams@...el.com>,
David Howells <dhowells@...hat.com>,
Steven Whitehouse <swhiteho@...hat.com>,
Mimi Zohar <zohar@...ux.vnet.ibm.com>,
linux-xfs@...r.kernel.org, linux-raid@...r.kernel.org,
linux-nvdimm@...ts.01.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 10/23] afs: switch to use uuid_t and uuid_gen
On Thu, 2017-05-25 at 15:00 +0200, Christoph Hellwig wrote:
> On Tue, May 23, 2017 at 04:11:39PM +0300, Andy Shevchenko wrote:
> > Since we introduced a union it's possible that we might access the
> > member which wasn't last modified one. So, my comment is to give an
> > attention on such possibility and avoid if there is an aliasing
> > happened.
>
> We do for AFS (and XFS for fs fsid). My preference would be to
> not have the v1 struct defintion but instead provide a few
> helpers in uuid.h that use get_unaligned_be* if needed:
>
> uuid_v1_time_low()
> uuid_v1_time_mid()
> uuid_v1_time_time_hi_and_version()..
>
> From his previously reply it seems like Dave doesn't like that idea
> too much, in which case I suspect moving struct uuid_v1 back into
> afs and living with cast in it is the way to go.
Personally I don't like that union stuff, so, definitely my vote to get
rid of AFS stuff in generic helpers.
OTOH if there will be more users of such API then something like you
proposed would be sufficient without introducing a union.
--
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Intel Finland Oy
Powered by blists - more mailing lists