On Tue, Jul 17, 2012 at 11:15:30AM -0700, John Stultz wrote:
> Attached are two tests. One is general exerciser of the leapsecond code 
> (leap-a-day) which also notes if it sees the hrtimer/futuex early 
> expiration issue, and the other is a much faster (almost immediate) 
> reproducer for the leapsecond deadlock (leapcrash).
> 
> The leapcrash test will likely wedge unpatched systems in hardirq 
> context, and has caused lost (dirty) data in my testing, so BEWARE!
> RUN AT YOUR OWN RISK!

Thank you, and nice note for the big warning above. I have some diskless
machines which don't risk anything, I will test there first :-)

Cheers,
Willy