linux-kernel - Re: [Tee-dev] [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 16:36:42 +0300
From:   Maxim Uvarov <maxim.uvarov@...aro.org>
To:     Jerome Forissier <jerome@...issier.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        "tee-dev @ lists . linaro . org" <tee-dev@...ts.linaro.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>,
        Jason Gunthorpe <jgg@...pe.ca>,
        Arnd Bergmann <arnd@...aro.org>,
        linux-integrity@...r.kernel.org, peterhuewe@....de
Subject: Re: [Tee-dev] [PATCHv3 2/3] optee: use uuid for sysfs driver entry

On Mon, 25 May 2020 at 15:10, Jerome Forissier <jerome@...issier.org> wrote:
>
>
>
> On 5/25/20 1:52 PM, Maxim Uvarov wrote:
> > Optee device names for sysfs needed to be unique
>
> s/Optee/OP-TEE/
> s/needed/need/
>
> > and it's better if they will mean something. UUID for name
> > looks like good solution:
> > /sys/bus/tee/devices/optee-clnt-<uuid>
>
> How about mentioning it is the UUID of the Trusted Application on the
> TEE side?
>

Jerome, do you think optee-ta-<uuid> is more suitable here?


> >
> > Signed-off-by: Maxim Uvarov <maxim.uvarov@...aro.org>
> > ---
> >  drivers/tee/optee/device.c | 6 +++---
> >  1 file changed, 3 insertions(+), 3 deletions(-)
>
> Thanks,
> --
> Jerome