[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.11.1601231710210.3886@nanos>
Date: Sat, 23 Jan 2016 17:11:54 +0100 (CET)
From: Thomas Gleixner <tglx@...utronix.de>
To: Ben Hutchings <ben@...adent.org.uk>
cc: Tejun Heo <tj@...nel.org>, Sasha Levin <sasha.levin@...cle.com>,
Jan Kara <jack@...e.cz>, Shaohua Li <shli@...com>,
LKML <linux-kernel@...r.kernel.org>, stable@...r.kernel.org,
Daniel Bilik <daniel.bilik@...system.cz>
Subject: Re: Crashes with 874bbfe600a6 in 3.18.25
On Sat, 23 Jan 2016, Ben Hutchings wrote:
> On Fri, 2016-01-22 at 11:09 -0500, Tejun Heo wrote:
> > > Looks like it requires more than trivial backport (I think). Tejun?
> >
> > The timer migration has changed quite a bit. Given that we've never
> > seen vmstat work crashing in 3.18 era, I wonder whether the right
> > thing to do here is reverting 874bbfe600a6 from 3.18 stable?
>
> It's not just 3.18 that has this; 874bbfe600a6 was backported to all
> stable branches from 3.10 onward. Only the 4.2-ckt branch has
> 22b886dd10180939.
22b886dd10180939 fixes a bug which was introduced with the timer wheel
overhaul in 4.2. So only 4.2/3 should have it backported.
Thanks,
tglx
Powered by blists - more mailing lists