linux-kernel - Re: new tree for linux-next: uuid

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 for Android: free password hash cracker in your pocket

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

Date:   Tue, 6 Jun 2017 00:29:14 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc:     Christoph Hellwig <hch@....de>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        linux-kernel@...r.kernel.org
Subject: Re: new tree for linux-next: uuid

Hi Andy,

On Mon, 05 Jun 2017 17:06:45 +0300 Andy Shevchenko <andriy.shevchenko@...ux.intel.com> wrote:
>
> On Mon, 2017-06-05 at 10:07 +0200, Christoph Hellwig wrote:
> > Meh, thanks.  This has been throught the buildbot countless times
> > without a report.  But I guess a less generic name might be a good
> > idea to start with.
> > 
> > Andy: do you think UUID_INIT/GUID_INIT make sense to your?
> > or _INITIALIZER?  
> 
> I'm a bit out of context. Where this will be used?

include/uapi/linux/uuid.h (after the uuid lib changes) contains a
definition of the macro GUID() which is probably a bit generic a name
for a uapi include file.  It also clashes with a couple of other uses
of that macro name already in the kernel (one of which produced several
warnings in linux-next today).

It produces an initializer for a guid_t (structure).

-- 
Cheers,
Stephen Rothwell