linux-kernel - Re: [stable] 2.6.32.21 - uptime related crashes?

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20111025232545.GB14714@1wt.eu>
Date:	Wed, 26 Oct 2011 01:25:45 +0200
From:	Willy Tarreau <w@....eu>
To:	john stultz <johnstul@...ibm.com>
Cc:	Ruben Kerkhof <ruben@...enkerkhof.com>, Greg KH <greg@...ah.com>,
	linux-kernel@...r.kernel.org, seto.hidetoshi@...fujitsu.com,
	Peter Zijlstra <peterz@...radead.org>,
	MINOURA Makoto <minoura@...inux.co.jp>,
	Ingo Molnar <mingo@...e.hu>, stable@...nel.org,
	Hervé Commowick <hcommowick@...sec.fr>,
	Rand@...per.es, Andrew Morton <akpm@...ux-foundation.org>,
	Faidon Liambotis <paravoid@...ian.org>
Subject: Re: [stable] 2.6.32.21 - uptime related crashes?

Hi John,

On Tue, Oct 25, 2011 at 03:44:30PM -0700, john stultz wrote:
> The softlockup false positive issue should have been fixed by Peter's
> "x86, intel: Don't mark sched_clock() as stable" below. But I'm not
> seeing it upstream.  Peter, is this still the right fix?

I've not seen any other one proposed, and both you and Peter appeared
to like it. I understood that Ingo was waiting for the merge window to
submit it and I think that it simply got lost.

Ingo, can you confirm ?

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