From: Vladimir Zapolskiy <vz@mleia.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH 2/2] crypto: s5p-sss - Handle unaligned buffers
Date: Mon, 7 Mar 2016 03:28:24 +0200 [thread overview]
Message-ID: <56DCD938.7090100@mleia.com> (raw)
In-Reply-To: <1457259436-32560-2-git-send-email-krzk@kernel.org>
Hi Krzysztof,
On 06.03.2016 12:17, Krzysztof Kozlowski wrote:
> During crypto selftests on Odroid XU3 (Exynos5422) some of the
> algorithms failed because of passing AES-block unaligned source and
> destination buffers:
excuse my ignorance what are the crypto selftests you reference? Are they
run-time self tests run by crypto manager on algorithm registration?
> alg: skcipher: encryption failed on chunk test 1 for ecb-aes-s5p: ret=22
>
> Handle such case by copying the buffers to a new aligned and contiguous
> space.
I'm not quite convinced that a particular crypto accelerator driver
is the right place for this change, at least I don't see in the change
anything S5P-SSS specific, but it might be good to add the change.
Briefly looking at other drivers similarly atmel-* and omap-* have
slow path fallbacks, ./rockchip/rk3288_crypto_ablkcipher.c fails like
s5p-sss etc.
Anyway since it is a valid improvement, please feel free to add my
Acked-by: Vladimir Zapolskiy <vz@mleia.com>
> Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
> ---
> drivers/crypto/s5p-sss.c | 149 +++++++++++++++++++++++++++++++++++++++++++----
> 1 file changed, 137 insertions(+), 12 deletions(-)
>
WARNING: multiple messages have this Message-ID (diff)
From: Vladimir Zapolskiy <vz@mleia.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH 2/2] crypto: s5p-sss - Handle unaligned buffers
Date: Mon, 7 Mar 2016 03:28:24 +0200 [thread overview]
Message-ID: <56DCD938.7090100@mleia.com> (raw)
In-Reply-To: <1457259436-32560-2-git-send-email-krzk@kernel.org>
Hi Krzysztof,
On 06.03.2016 12:17, Krzysztof Kozlowski wrote:
> During crypto selftests on Odroid XU3 (Exynos5422) some of the
> algorithms failed because of passing AES-block unaligned source and
> destination buffers:
excuse my ignorance what are the crypto selftests you reference? Are they
run-time self tests run by crypto manager on algorithm registration?
> alg: skcipher: encryption failed on chunk test 1 for ecb-aes-s5p: ret=22
>
> Handle such case by copying the buffers to a new aligned and contiguous
> space.
I'm not quite convinced that a particular crypto accelerator driver
is the right place for this change, at least I don't see in the change
anything S5P-SSS specific, but it might be good to add the change.
Briefly looking at other drivers similarly atmel-* and omap-* have
slow path fallbacks, ./rockchip/rk3288_crypto_ablkcipher.c fails like
s5p-sss etc.
Anyway since it is a valid improvement, please feel free to add my
Acked-by: Vladimir Zapolskiy <vz@mleia.com>
> Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
> ---
> drivers/crypto/s5p-sss.c | 149 +++++++++++++++++++++++++++++++++++++++++++----
> 1 file changed, 137 insertions(+), 12 deletions(-)
>
--
With best wishes,
Vladimir
next prev parent reply other threads:[~2016-03-07 1:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-06 10:17 [PATCH 1/2] crypto: s5p-sss - Minor coding cleanups Krzysztof Kozlowski
2016-03-06 10:17 ` [PATCH 2/2] crypto: s5p-sss - Handle unaligned buffers Krzysztof Kozlowski
2016-03-07 1:28 ` Vladimir Zapolskiy [this message]
2016-03-07 1:28 ` Vladimir Zapolskiy
2016-03-07 3:59 ` Krzysztof Kozlowski
2016-03-07 1:01 ` [PATCH 1/2] crypto: s5p-sss - Minor coding cleanups Vladimir Zapolskiy
2016-03-07 4:05 ` Krzysztof Kozlowski
2016-03-09 23:40 ` Vladimir Zapolskiy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56DCD938.7090100@mleia.com \
--to=vz@mleia.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=krzk@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.