From: Zeev Zilberman <zeev@annapurnaLabs.com>
To: "linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>
Subject: ahash and crc32c
Date: Tue, 26 Feb 2013 17:11:55 +0000 [thread overview]
Message-ID: <CD52BAD7.26798%zeev@annapurnalabs.com> (raw)
Hi,
I'm working on an ahash driver that supports CRC32C.
I saw that all existing CRC32C implementations (except blackfin) are
implementing shash interface, but ahash seems to be the correct choice
in our case.
On the other hand I saw that CRC32C test in testmgr.c tries to create
shash tfm for CRC32C and assumes that the CRC context is saved in first
4 bytes of the shash context.
When I implement CRC32C algorithm this part of the test fails.
How should I treat this failure? What is the reason for the requirement
that is tested in this scenario?
Thank you.
Zeev.
next reply other threads:[~2013-02-26 17:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 17:11 Zeev Zilberman [this message]
2016-10-28 12:46 ` ahash and crc32c Horia Geanta Neag
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=CD52BAD7.26798%zeev@annapurnalabs.com \
--to=zeev@annapurnalabs.com \
--cc=linux-crypto@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