From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: paulmck@linux.vnet.ibm.com
Cc: Thomas Gleixner <tglx@linutronix.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [GIT pull] timer fixes for .27
Date: Tue, 30 Sep 2008 13:41:56 +1000 [thread overview]
Message-ID: <1222746116.9006.23.camel@pasglop> (raw)
In-Reply-To: <20080929224440.GG6697@linux.vnet.ibm.com>
On Mon, 2008-09-29 at 15:44 -0700, Paul E. McKenney wrote:
> > Please pull the latest timers-fixes-for-linus git tree from:
> >
> >
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git
> timers-fixes-for-linus
> >
> > The patches fix hard to trigger bugs in the CPU offline code of
> > hrtimers which were noticed by Paul McKenney recently. In the worst
> > case they can leave migrated hrtimers in a stale state.
>
> Acked-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> Tested-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Ah, so we found and fixed these ?
Linus, those bugs are actually a regression from when we didn't use the
new timer code (which isn't that long ago). It would be nice to have the
fixes in .27 (and thus in the various distros that will derive from it)
but I would understand if the size of the patch made you choke that late
in the -rc cycle... In which case we'll be in for more backports :-)
Cheers,
Ben.
next prev parent reply other threads:[~2008-09-30 3:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-29 22:15 [GIT pull] timer fixes for .27 Thomas Gleixner
2008-09-29 22:44 ` Paul E. McKenney
2008-09-30 3:41 ` Benjamin Herrenschmidt [this message]
2008-09-30 3:54 ` Paul E. McKenney
2008-09-30 4:02 ` Paul E. McKenney
2008-09-30 14:34 ` Linus Torvalds
2008-09-30 15:16 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2008-07-27 20:15 Thomas Gleixner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1222746116.9006.23.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulmck@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox