linux-kernel - Re: [PATCHv3 2/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: Windows password security audit tool. GUI, reports in PDF.

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

Date:   Mon, 25 May 2020 14:47:53 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Maxim Uvarov <maxim.uvarov@...aro.org>
Cc:     linux-kernel@...r.kernel.org, tee-dev@...ts.linaro.org,
        peterhuewe@....de, jarkko.sakkinen@...ux.intel.com, jgg@...pe.ca,
        jens.wiklander@...aro.org, linux-integrity@...r.kernel.org,
        arnd@...aro.org, sumit.garg@...aro.org
Subject: Re: [PATCHv3 2/3] optee: use uuid for sysfs driver entry

On Mon, May 25, 2020 at 02:52:34PM +0300, Maxim Uvarov wrote:
> Optee device names for sysfs needed to be unique
> and it's better if they will mean something. UUID for name
> looks like good solution:
> /sys/bus/tee/devices/optee-clnt-<uuid>

Can you document that in Documentation/ABI/ ?

And why UUID?  Those are usually huge, is that easier than just a unique
number?

thanks,

greg k-h