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: <1366222033.27102.104.camel@schen9-DESK>
Date:	Wed, 17 Apr 2013 11:07:13 -0700
From:	Tim Chen <tim.c.chen@...ux.intel.com>
To:	Jussi Kivilinna <jussi.kivilinna@....fi>
Cc:	Herbert Xu <herbert@...dor.apana.org.au>,
	"H. Peter Anvin" <hpa@...or.com>,
	"David S. Miller" <davem@...emloft.net>,
	"Martin K. Petersen" <martin.petersen@...cle.com>,
	James Bottomley <James.Bottomley@...senPartnership.com>,
	Matthew Wilcox <willy@...ux.intel.com>,
	Jim Kukunas <james.t.kukunas@...ux.intel.com>,
	Keith Busch <keith.busch@...el.com>,
	Erdinc Ozturk <erdinc.ozturk@...el.com>,
	Vinodh Gopal <vinodh.gopal@...el.com>,
	James Guilford <james.guilford@...el.com>,
	Wajdi Feghali <wajdi.k.feghali@...el.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	linux-crypto@...r.kernel.org, linux-scsi@...r.kernel.org
Subject: Re: [PATCH 4/4] Simple correctness and speed test for CRCT10DIF
 hash

On Wed, 2013-04-17 at 20:58 +0300, Jussi Kivilinna wrote:
> On 16.04.2013 19:20, Tim Chen wrote:
> > These are simple tests to do sanity check of CRC T10 DIF hash.  The
> > correctness of the transform can be checked with the command
> > 	modprobe tcrypt mode=47
> > The speed of the transform can be evaluated with the command
> > 	modprobe tcrypt mode=320
> > 
> > Set the cpu frequency to constant and turn turbo off when running the
> > speed test so the frequency governor will not tweak the frequency and
> > affects the measurements.
> > 
> > Signed-off-by: Tim Chen <tim.c.chen@...ux.intel.com>
> > Tested-by: Keith Busch <keith.busch@...el.com>
> <snip>
> >  
> > +#define CRCT10DIF_TEST_VECTORS	2
> > +static struct hash_testvec crct10dif_tv_template[] = {
> > +	{
> > +		.plaintext = "abc",
> > +		.psize  = 3,
> > +#ifdef __LITTLE_ENDIAN
> > +		.digest = "\x3b\x44",
> > +#else
> > +		.digest = "\x44\x3b",
> > +#endif
> > +	}, {
> > +		.plaintext =
> > +		"abcddddddddddddddddddddddddddddddddddddddddddddddddddddd",
> > +		.psize  = 56,
> > +#ifdef __LITTLE_ENDIAN
> > +		.digest = "\xe3\x9c",
> > +#else
> > +		.digest = "\x9c\xe3",
> > +#endif
> > +		.np     = 2,
> > +		.tap    = { 28, 28 }
> > +	}
> > +};
> > +
> 
> Are these large enough to test all code paths in the PCLMULQDQ implementation?

We have tested the implementation exhaustively for large number of code paths.
The tcrypt tests here are only meant for sanity check, and not for
exhaustive tests.

Tim


--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ