[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1322870543.21423.186.camel@work-vm>
Date: Fri, 02 Dec 2011 16:02:23 -0800
From: john stultz <johnstul@...ibm.com>
To: Greg KH <greg@...ah.com>
Cc: Willy Tarreau <w@....eu>, Ruben Kerkhof <ruben@...enkerkhof.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?
On Fri, 2011-12-02 at 15:45 -0800, Greg KH wrote:
> On Wed, Oct 26, 2011 at 01:25:45AM +0200, Willy Tarreau wrote:
> > 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 ?
>
> I'm totally confused here, what's the status of this, and what exactly
> is the patch?
Ingo has the fix from Salman queued in -tip, but I'm not sure why its
not been pushed to Linus yet.
http://git.kernel.org/?p=linux/kernel/git/tip/tip.git;a=commit;h=4cecf6d401a01d054afc1e5f605bcbfe553cb9b9
thanks
-john
--
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/
Powered by blists - more mailing lists