[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190502120012.GA19008@Red>
Date: Thu, 2 May 2019 14:00:12 +0200
From: Corentin Labbe <clabbe.montjoie@...il.com>
To: Kalyani Akula <kalyani.akula@...inx.com>
Cc: herbert@...dor.apana.org.au, kstewart@...uxfoundation.org,
gregkh@...uxfoundation.org, tglx@...utronix.de,
pombredanne@...b.com, linux-crypto@...r.kernel.org,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
saratcha@...inx.com, Kalyani Akula <kalyania@...inx.com>
Subject: Re: [RFC PATCH V3 0/4] Add Xilinx's ZynqMP SHA3 driver support
On Thu, May 02, 2019 at 04:04:38PM +0530, Kalyani Akula wrote:
> This patch set adds support for
> - dt-binding docs for Xilinx ZynqMP SHA3 driver
> - Adds communication layer support for sha_hash in zynqmp.c
> - Adds Xilinx ZynqMP driver for SHA3 Algorithm
> - Adds device tree node for ZynqMP SHA3 driver
>
> V3 Changes :
> - Removed zynqmp_sha_import and export APIs.The reason as follows
> The user space code does an accept on an already accepted FD
> when we create AF_ALG socket and call accept on it,
> it calls af_alg_accept and not hash_accept.
> import and export APIs are called from hash_accept.
> The flow is as below
> accept--> af_alg_accept-->hash_accept_parent-->hash_accept_parent_nokey
> for hash salg_type.
> - Resolved comments from
> https://patchwork.kernel.org/patch/10753719/
>
Your driver still doesnt handle the case where two hash are done in parallel.
Furthermore, you miss the export/import functions.
Regards
Powered by blists - more mailing lists