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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <DB7PR04MB4620E3087C59A26B865DEE988B790@DB7PR04MB4620.eurprd04.prod.outlook.com>
Date:   Wed, 6 Nov 2019 07:27:56 +0000
From:   Vakul Garg <vakul.garg@....com>
To:     Andrey Smirnov <andrew.smirnov@...il.com>,
        "linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org>
CC:     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" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 0/5] CAAM JR lifecycle



> -----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?


>  drivers/crypto/caam/Kconfig      |   5 +-
>  drivers/crypto/caam/Makefile     |  15 +--
>  drivers/crypto/caam/caamalg.c    | 114 ++++++++++----------
>  drivers/crypto/caam/caamalg_qi.c |  12 +--
>  drivers/crypto/caam/caamhash.c   | 117 +++++++++++----------
>  drivers/crypto/caam/caampkc.c    |  67 ++++++------
>  drivers/crypto/caam/caampkc.h    |   2 +-
>  drivers/crypto/caam/caamrng.c    |  41 ++++----
>  drivers/crypto/caam/ctrl.c       |  16 ++-
>  drivers/crypto/caam/intern.h     |   3 +-
>  drivers/crypto/caam/jr.c         | 173 ++++++++-----------------------
>  drivers/crypto/caam/jr.h         |  14 ++-
>  drivers/crypto/caam/key_gen.c    |  11 +-
>  drivers/crypto/caam/key_gen.h    |   5 +-
>  14 files changed, 275 insertions(+), 320 deletions(-)
> 
> --
> 2.21.0