linux-kernel - Re: [PATCH 0/5] CAAM JR lifecycle

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]

Message-ID: <VI1PR0402MB34851C1681F8A18341A8971098760@VI1PR0402MB3485.eurprd04.prod.outlook.com>
Date:   Wed, 13 Nov 2019 18:57:19 +0000
From:   Horia Geanta <horia.geanta@....com>
To:     Andrey Smirnov <andrew.smirnov@...il.com>,
        Vakul Garg <vakul.garg@....com>
CC:     "linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org>,
        Chris Healy <cphealy@...il.com>,
        Lucas Stach <l.stach@...gutronix.de>,
        Herbert Xu <herbert@...dor.apana.org.au>,
        Iuliana Prodan <iuliana.prodan@....com>,
        dl-linux-imx <linux-imx@....com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/5] CAAM JR lifecycle

On 11/6/2019 5:19 PM, Andrey Smirnov wrote:
> On Tue, Nov 5, 2019 at 11:27 PM Vakul Garg <vakul.garg@....com> wrote:
>>
>>
>>
>>> -----Original Message-----
>>> From: linux-crypto-owner@...r.kernel.org <linux-crypto-
>>> owner@...r.kernel.org> On Behalf Of Andrey Smirnov
>>> Sent: Tuesday, November 5, 2019 8:44 PM
>>> To: linux-crypto@...r.kernel.org
>>> Cc: Andrey Smirnov <andrew.smirnov@...il.com>; Chris Healy
>>> <cphealy@...il.com>; Lucas Stach <l.stach@...gutronix.de>; Horia Geanta
>>> <horia.geanta@....com>; Herbert Xu <herbert@...dor.apana.org.au>;
>>> Iuliana Prodan <iuliana.prodan@....com>; dl-linux-imx <linux-
>>> imx@....com>; linux-kernel@...r.kernel.org
>>> Subject: [PATCH 0/5] CAAM JR lifecycle
>>>
>>> Everyone:
>>>
>>> This series is a different approach to addressing the issues brought up in
>>> [discussion]. This time the proposition is to get away from creating per-JR
>>> platfrom device, move all of the underlying code into caam.ko and disable
>>> manual binding/unbinding of the CAAM device via sysfs. Note that this series
>>> is a rough cut intented to gauge if this approach could be acceptable for
>>> upstreaming.
>>>
>>> Thanks,
>>> Andrey Smirnov
>>>
>>> [discussion] lore.kernel.org/lkml/20190904023515.7107-13-
>>> andrew.smirnov@...il.com
>>>
>>> Andrey Smirnov (5):
>>>   crypto: caam - use static initialization
>>>   crypto: caam - introduce caam_jr_cbk
>>>   crypto: caam - convert JR API to use struct caam_drv_private_jr
>>>   crypto: caam - do not create a platform devices for JRs
>>>   crypto: caam - disable CAAM's bind/unbind attributes
>>>
>>
>> To access caam jobrings from DPDK (user space drivers), we unbind job-ring's platform device from the kernel.
>> What would be the alternate way to enable job ring drivers in user space?
>>
> 
> Wouldn't either building your kernel with
> CONFIG_CRYPTO_DEV_FSL_CAAM_JR=n (this series doesn't handle that right
> currently due to being a rough cut) or disabling specific/all JRs via
> DT accomplish the same goal?
> 
It's not a 1:1 match, the ability to move a ring to user space / VM etc.
*dynamically* goes away.

Horia