linux-kernel - Re: [PATCH 00/11] 3.0-stable: Fix for leapsecond deadlock & hrtimer/futex issue

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: <20120717190553.GA4140@1wt.eu>
Date:	Tue, 17 Jul 2012 21:05:53 +0200
From:	Willy Tarreau <w@....eu>
To:	John Stultz <johnstul@...ibm.com>
Cc:	stable@...r.kernel.org, Prarit Bhargava <prarit@...hat.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 00/11] 3.0-stable: Fix for leapsecond deadlock & hrtimer/futex issue

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

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