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

[Andi Kleen <andi@firstfloor.org>]

> 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