From: Jens Axboe <axboe@kernel.dk>
To: Corentin Labbe <clabbe.montjoie@gmail.com>,
herbert@gondor.apana.org.au, kbusch@kernel.org
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: crypto: crc64-rocksoft-generic test failed (wrong result) on test vector 0
Date: Tue, 22 Mar 2022 07:02:20 -0600 [thread overview]
Message-ID: <650655da-e719-4e48-5dc5-2e6529674f65@kernel.dk> (raw)
In-Reply-To: <YjmeVttXDd/FPwUP@Red>
On 3/22/22 4:00 AM, Corentin Labbe wrote:
> Hello
>
> Booting an arm64_defconfig with BigEndian lead to:
> alg: shash: crc64-rocksoft-generic test failed (wrong result) on test vector 0, cfg=\"init+update+final aligned buffer\"
>
> Reproductible on the virt qemu machine.
>
> Furthermore, none of crc64 files have clear MAINTAINERS entry.
Keith, can you send in your BE fix? The commit is upstream now.
--
Jens Axboe
prev parent reply other threads:[~2022-03-22 13:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 10:00 crypto: crc64-rocksoft-generic test failed (wrong result) on test vector 0 Corentin Labbe
2022-03-22 13:02 ` Jens Axboe [this message]
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=650655da-e719-4e48-5dc5-2e6529674f65@kernel.dk \
--to=axboe@kernel.dk \
--cc=clabbe.montjoie@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=kbusch@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).