linux-kernel - Re: [PATCH REPOST for 2.6.25] Use an own random generator for pageattr-test.c

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20080311221144.GC428@one.firstfloor.org>
Date:	Tue, 11 Mar 2008 23:11:44 +0100
From:	Andi Kleen <andi@...stfloor.org>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Andi Kleen <andi@...stfloor.org>, Ingo Molnar <mingo@...e.hu>,
	linux-kernel@...r.kernel.org, akpm@...l.org
Subject: Re: [PATCH REPOST for 2.6.25] Use an own random generator for pageattr-test.c

> The only bug that code ever caught aside of tons of false positives

It caught bugs when I originally worked on cpa. However that 
had still the revert code and admittedly several were in 
that area (I'm still suspecting at some point you'll have
to readd that -- perhaps it'll be more useful for you then)

However I had originally a longer runtime length too, but later
decreased it when I sent out the patch (since i didn't want 
to submit another "rcu torture" which runs for hours...) 
Perhaps the result was a little too short too, that's possible.

> Finding a bug, when it was exposed by a static pattern, is trivial,
> but the challenge is to make such tests useful enough with random
> patterns. And there are ways to do that, e.g. by making the debug
> output informative enough to provide information about the problem in
> detail instead of printing some useless info "a != b".

Ok I admit I don't know how to do that effectively for cpa, but perhaps
you do.

-Andi

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