linux-kernel - Re: [Tee-dev] [PATCHv8 1/3] optee: use uuid for sysfs driver entry

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:   Fri, 26 Jun 2020 11:47:36 +0300
From:   Andy Shevchenko <andy.shevchenko@...il.com>
To:     Sumit Garg <sumit.garg@...aro.org>
Cc:     Maxim Uvarov <maxim.uvarov@...aro.org>,
        Jerome Forissier <jerome@...issier.org>,
        James Bottomley <James.Bottomley@...senpartnership.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>,
        Arnd Bergmann <arnd@...aro.org>,
        "tee-dev @ lists . linaro . org" <tee-dev@...ts.linaro.org>,
        Jason Gunthorpe <jgg@...pe.ca>,
        linux-integrity <linux-integrity@...r.kernel.org>,
        peterhuewe@....de
Subject: Re: [Tee-dev] [PATCHv8 1/3] optee: use uuid for sysfs driver entry

On Fri, Jun 26, 2020 at 8:18 AM Sumit Garg <sumit.garg@...aro.org> wrote:
> On Thu, 25 Jun 2020 at 18:22, Maxim Uvarov <maxim.uvarov@...aro.org> wrote:

...

> I guess you missed the point that uuid_t is implemented in BE format
> in the kernel which is compliant as per RFC 4122.

I guess you missed the point. Kernel doesn't have anything special
about these types and does NOT compliant as per RFC.
The only things the kernel distinguishes are a) byte order (always),
and b) version bits when you get a random UUID (whatever you call it).

I guess this discussion takes too much time. The idea is that kernel
types are just for kernel use with as little intrusion as possible.
The main principle, we get something, we carry it w/o modifications
inside the kernel.

So, you may use whatever you want and LE/BE is purely based on a) and b) above.

-- 
With Best Regards,
Andy Shevchenko