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]
Date:	Wed, 12 Oct 2011 09:06:01 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>
Cc:	Andi Kleen <andi@...stfloor.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Stephane Eranian <eranian@...gle.com>,
	linux-kernel@...r.kernel.org, acme@...hat.com,
	ming.m.lin@...el.com, robert.richter@....com, ravitillo@....gov
Subject: Re: [PATCH 07/12] perf_events: add LBR software filter support for
 Intel X86


* Masami Hiramatsu <masami.hiramatsu.pt@...achi.com> wrote:

> (2011/10/10 23:45), Andi Kleen wrote:
> >> Ah, nice. Maybe we need another test binary, since current one is
> >> just ensuring the output of objdump and decoder is same.
> >> anyway it's not so difficult if it feeds random binaries to
> >> ensure the decoder doesn't access bad address.
> > 
> > Pure /dev/urandom is not good because it cannot be ever reproduced.
> > Better use a PRNG with random seed from urandom, but print the seed.
> 
> Sure,

Obviously the urandom data should be kbuild generated and only 
cleared on 'make clean' - not regenerated on every run. So if there's 
a failure the failing urandom data stays around readily.

Thanks,

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