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: <20110904232657.GC6749@tty.gr>
Date:	Mon, 5 Sep 2011 02:26:58 +0300
From:	Faidon Liambotis <paravoid@...ian.org>
To:	Greg KH <greg@...ah.com>
Cc:	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>,
	john stultz <johnstul@...ibm.com>, Rand@...per.es,
	Andrew Morton <akpm@...ux-foundation.org>,
	Willy Tarreau <w@....eu>
Subject: Re: [stable] 2.6.32.21 - uptime related crashes?

On Tue, Aug 30, 2011 at 03:38:29PM -0700, Greg KH wrote:
> On Thu, Aug 25, 2011 at 09:56:16PM +0300, Faidon Liambotis wrote:
> > On Thu, Jul 21, 2011 at 08:45:25PM +0200, Ingo Molnar wrote:
> > > * Peter Zijlstra <peterz@...radead.org> wrote:
> > > 
> > > > On Thu, 2011-07-21 at 14:50 +0200, Nikola Ciprich wrote:
> > > > > thanks for the patch! I'll put this on our testing boxes...
> > > > 
> > > > With a patch that frobs the starting value close to overflowing I hope,
> > > > otherwise we'll not hear from you in like 7 months ;-)
> > > > 
> > > > > Are You going to push this upstream so we can ask Greg to push this to
> > > > > -stable? 
> > > > 
> > > > Yeah, I think we want to commit this with a -stable tag, Ingo?
> > > 
> > > yeah - and we also want a Reported-by tag and an explanation of how 
> > > it can crash and why it matters in practice. I can then stick it into 
> > > the urgent branch for Linus. (probably will only hit upstream in the 
> > > merge window though.)
> > 
> > Has this been pushed or has the problem been solved somehow? Time is
> > against us on this bug as more boxes will crash as they reach 200 days
> > of uptime...
> > 
> > In any case, feel free to use me as a Reported-by, my full report of the
> > problem being <20110430173905.GA25641@....gr>.
> > 
> > FWIW and if I understand correctly, my symptoms were caused by *two*
> > different bugs:
> > a) the 54 bits wraparound at 208 days that Peter fixed above,
> > b) a kernel crash at ~215 days related to RT tasks, fixed by
> > 305e6835e05513406fa12820e40e4a8ecb63743c (already in -stable).
> 
> So, what do I do here as part of the .32-longterm kernel?  Is there a
> fix that is in Linus's tree that I need to apply here?
> 
> confused,

Is this even pushed upstream? I checked Linus' tree and the proposed
patch is *not* merged there. I'm not really sure if it was fixed some
other way, though. I thought this was intended to be an "urgent" fix or
something?

Regards,
Faidon
--
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/