Messages in this thread |  | | Subject | Re: [PATCH v2 0/4] Additional fixes on Talitos driver | From | Christophe Leroy <> | Date | Tue, 11 Jun 2019 19:16:30 +0200 |
| |
Le 11/06/2019 à 18:30, Horia Geanta a écrit : > On 6/11/2019 6:40 PM, Christophe Leroy wrote: >> >> >> Le 11/06/2019 à 17:37, Horia Geanta a écrit : >>> On 6/11/2019 5:39 PM, Christophe Leroy wrote: >>>> This series is the last set of fixes for the Talitos driver. >>>> >>>> We now get a fully clean boot on both SEC1 (SEC1.2 on mpc885) and >>>> SEC2 (SEC2.2 on mpc8321E) with CONFIG_CRYPTO_MANAGER_EXTRA_TESTS: >>>> >>> I am getting below failures on a sec 3.3.2 (p1020rdb) for hmac(sha384) and >>> hmac(sha512): >> >> Is that new with this series or did you already have it before ? >> > Looks like this happens with or without this series. > > I haven't checked the state of this driver for quite some time. > Since I've noticed increased activity, I thought it would be worth > actually testing the changes. > > Are changes in patch 2/4 ("crypto: talitos - fix hash on SEC1.") > strictly for sec 1.x or they affect all revisions?
They are strictly for sec 1.x
> >> What do you mean by "fuzz testing" enabled ? Is that >> CONFIG_CRYPTO_MANAGER_EXTRA_TESTS or something else ? >> > Yes, it's this config symbol.
Indeed SEC 2.2 only supports up to SHA-256.
Christophe
> > Horia >
|  |