[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130424224218.GA7767@roeck-us.net>
Date: Wed, 24 Apr 2013 15:42:18 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: Prarit Bhargava <prarit@...hat.com>
Cc: John Stultz <john.stultz@...aro.org>, linux-kernel@...r.kernel.org,
Thomas Gleixner <tglx@...utronix.de>,
stable <stable@...r.kernel.org>
Subject: Re: [PATCH] hrtimer, add expiry time overflow check in
hrtimer_interrupt
On Mon, Apr 08, 2013 at 04:34:26PM -0400, Prarit Bhargava wrote:
>
>
> On 04/08/2013 04:19 PM, John Stultz wrote:
> > On 04/08/2013 05:47 AM, Prarit Bhargava wrote:
>
> >>
> >> A simple check for an overflow can resolve this problem. Using KTIME_MAX
> >> instead of the overflow value will result in the hrtimer function being run,
> >> and the reprogramming of the timer after that.
> >>
> >> Signed-off-by: Prarit Bhargava <prarit@...hat.com>
> >> Cc: Thomas Gleixner <tglx@...utronix.de>
> >> Cc: John Stultz <john.stultz@...aro.org>
> >
> > Prarit: Should this be tagged for -stable?
>
> John,
>
> Yes, this should go to -stable. cc'd.
>
Hi,
I am a bit surprised that this patch has not found its way into mainline yet,
as everyone seems to agree that it is a candidate for -stable.
I hit this problem very reliably (ie with each boot) with 3.8.x on systems
which have no RTC and run systemd. Seen with Freescale P5040 as well as
a Broadcom MIPS based system.
Guenter
--
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