linux-kernel - Re: [PATCH 3/3] crc32c: Implement a self-test for CRC32c

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110901064111.GA27893@gondor.apana.org.au>
Date:	Thu, 1 Sep 2011 14:41:11 +0800
From:	Herbert Xu <herbert@...dor.apana.org.au>
To:	Bob Pearson <rpearson@...temfabricworks.com>
Cc:	"'Darrick J. Wong'" <djwong@...ibm.com>,
	'Andreas Dilger' <adilger.kernel@...ger.ca>,
	'Theodore Tso' <tytso@....edu>,
	'David Miller' <davem@...emloft.net>,
	'linux-kernel' <linux-kernel@...r.kernel.org>,
	'Mingming Cao' <cmm@...ibm.com>,
	'linux-crypto' <linux-crypto@...r.kernel.org>,
	'linux-fsdevel' <linux-fsdevel@...r.kernel.org>,
	linux-ext4@...r.kernel.org
Subject: Re: [PATCH 3/3] crc32c: Implement a self-test for CRC32c

On Thu, Sep 01, 2011 at 12:40:08AM -0500, Bob Pearson wrote:
> Hi Darrick,
> 
> The same code in crc32.c was helpful to measure performance and help code tuning as well as indicate correctness. Otherwise the code in crypto may be enough to test all the corner cases. If this survives the review I wonder if there is a way to combine crc32 and crc32c together somehow. I like yours because you can load/unload and not need the memory permanently.

You can unload the crypto testmgr module too.

Cheers,
-- 
Email: Herbert Xu <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/