From: Kamil Konieczny <k.konieczny@partner.samsung.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Pascal Van Leeuwen <pvanleeuwen@insidesecure.com>
Cc: Eric Biggers <ebiggers@kernel.org>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>
Subject: Re: another testmgr question
Date: Fri, 24 May 2019 09:04:00 +0200 [thread overview]
Message-ID: <bbf4749b-9f7c-90d3-9adc-72e96467d0c4@partner.samsung.com> (raw)
In-Reply-To: <CAKv+Gu9F8EcDE8GRSyHFUh_pPXPJDziw7hXO=G4nA31PomDZ1g@mail.gmail.com>
On 24.05.2019 07:24, Ard Biesheuvel wrote:
> On Thu, 23 May 2019 at 22:44, Pascal Van Leeuwen
> <pvanleeuwen@insidesecure.com> wrote:
>>
> [...]
> In fact, given the above, I am slightly shocked that your hardware
> does not handle empty messages correctly. [...]
Imho hardware handles it in the way it was designed, for Exynos
writing non-zero value to len message register starts hash/hmac.
Writing zero and waiting for result will cause hang, as there will be
no result ever.
It can be done in HW to handle zero with additional register and more wires,
but it was left to software driver as trivial case.
--
Best regards,
Kamil Konieczny
Samsung R&D Institute Poland
next prev parent reply other threads:[~2019-05-24 7:04 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AM6PR09MB3523CED0B1587FCBDE4095A0D2010@AM6PR09MB3523.eurprd09.prod.outlook.com>
[not found] ` <20190523185833.GA243994@google.com>
2019-05-23 19:32 ` another testmgr question Pascal Van Leeuwen
2019-05-23 20:05 ` Eric Biggers
2019-05-23 21:43 ` Pascal Van Leeuwen
2019-05-23 23:48 ` Eric Biggers
2019-05-24 8:44 ` Pascal Van Leeuwen
2019-05-24 8:46 ` Christophe Leroy
2019-05-24 8:49 ` Jeffrey Walton
2019-05-24 9:42 ` Pascal Van Leeuwen
2019-05-24 9:21 ` Pascal Van Leeuwen
2019-05-24 9:25 ` Ard Biesheuvel
2019-05-24 9:34 ` Pascal Van Leeuwen
2019-05-24 9:45 ` Ard Biesheuvel
2019-05-24 9:57 ` Pascal Van Leeuwen
2019-05-24 11:09 ` Ard Biesheuvel
2019-05-27 9:52 ` Pascal Van Leeuwen
2019-05-24 10:13 ` Pascal Van Leeuwen
2019-05-24 10:43 ` Kamil Konieczny
2019-05-24 10:54 ` Christophe Leroy
2019-05-27 9:44 ` Pascal Van Leeuwen
2019-05-27 9:49 ` Ard Biesheuvel
2019-05-27 10:04 ` Pascal Van Leeuwen
2019-05-27 10:28 ` Ard Biesheuvel
2019-05-27 10:43 ` Pascal Van Leeuwen
2019-05-27 10:57 ` Ard Biesheuvel
2019-05-27 12:22 ` Pascal Van Leeuwen
2019-05-27 14:59 ` Ard Biesheuvel
2019-05-27 15:56 ` Pascal Van Leeuwen
2019-05-27 16:21 ` Ard Biesheuvel
2019-05-27 20:15 ` Pascal Van Leeuwen
2019-05-27 12:41 ` Pascal Van Leeuwen
2019-05-27 14:45 ` Ard Biesheuvel
2019-05-27 15:16 ` Pascal Van Leeuwen
2019-05-27 15:24 ` Ard Biesheuvel
2019-05-27 20:46 ` Pascal Van Leeuwen
2019-05-25 1:22 ` Eric Biggers
2019-05-27 9:55 ` Pascal Van Leeuwen
2019-05-24 9:27 ` Stephan Mueller
2019-05-24 5:24 ` Ard Biesheuvel
2019-05-24 7:04 ` Kamil Konieczny [this message]
2019-05-24 7:47 ` Pascal Van Leeuwen
2019-05-24 9:15 ` Ard Biesheuvel
2019-05-24 9:28 ` Pascal Van Leeuwen
2019-05-24 6:21 ` Christophe Leroy
2019-05-24 8:04 ` Pascal Van Leeuwen
2019-05-24 6:14 ` Jeffrey Walton
2019-05-24 8:00 ` Pascal Van Leeuwen
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=bbf4749b-9f7c-90d3-9adc-72e96467d0c4@partner.samsung.com \
--to=k.konieczny@partner.samsung.com \
--cc=ard.biesheuvel@linaro.org \
--cc=ebiggers@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=pvanleeuwen@insidesecure.com \
/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.