From: Sean Anderson <sean.anderson@seco.com>
To: Christian Eggers <ceggers@arri.de>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>
Cc: Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
linux-crypto@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: encryption test failures since "crypto: mxs-dcp - Use sg_mapping_iter to copy data"
Date: Thu, 27 Jan 2022 12:31:48 -0500 [thread overview]
Message-ID: <414858de-f279-c5ce-83ca-5c28d6c847b1@seco.com> (raw)
In-Reply-To: <2126453.Icojqenx9y@localhost.localdomain>
Hi Christian,
On 1/27/22 12:23 PM, Christian Eggers wrote:
> SoC: i.MX6ULL
>
> After upgrading from v5.10.65-rt53 to v5.10.73-rt54 I get two additional messages on boot:
>
> ...
> [ 3.786333] alg: skcipher: ecb-aes-dcp encryption test failed (wrong result) on test vector 0, cfg="two even aligned splits"
> [ 3.789020] alg: skcipher: cbc-aes-dcp encryption test failed (wrong result) on test vector 0, cfg="two even aligned splits"
> [ 3.793741] mxs-dcp 2280000.crypto: mxs_dcp: initialized
> ..
>
> After reverting the commit
>
> 2e6d793e1bf0 ("crypto: mxs-dcp - Use sg_mapping_iter to copy data")
>
> the error messages above disappear again.
Can you try applying the patch in [1] on top of your revert?
--Sean
[1] https://lore.kernel.org/linux-arm-kernel/20210701185638.3437487-1-sean.anderson@seco.com/
next prev parent reply other threads:[~2022-01-27 17:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 17:23 PROBLEM: encryption test failures since "crypto: mxs-dcp - Use sg_mapping_iter to copy data" Christian Eggers
2022-01-27 17:31 ` Sean Anderson [this message]
2022-01-27 18:09 ` Christian Eggers
2022-01-28 2:58 ` Herbert Xu
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=414858de-f279-c5ce-83ca-5c28d6c847b1@seco.com \
--to=sean.anderson@seco.com \
--cc=ceggers@arri.de \
--cc=davem@davemloft.net \
--cc=festevam@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox