From: Guenter Roeck <linux@roeck-us.net>
To: Prarit Bhargava <prarit@redhat.com>
Cc: John Stultz <john.stultz@linaro.org>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
stable <stable@vger.kernel.org>
Subject: Re: [PATCH] hrtimer, add expiry time overflow check in hrtimer_interrupt
Date: Wed, 24 Apr 2013 15:42:18 -0700 [thread overview]
Message-ID: <20130424224218.GA7767@roeck-us.net> (raw)
In-Reply-To: <516329D2.1050003@redhat.com>
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@redhat.com>
> >> Cc: Thomas Gleixner <tglx@linutronix.de>
> >> Cc: John Stultz <john.stultz@linaro.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
next prev parent reply other threads:[~2013-04-24 22:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 12:47 [PATCH] hrtimer, add expiry time overflow check in hrtimer_interrupt Prarit Bhargava
2013-04-08 14:53 ` Rik van Riel
2013-04-08 19:51 ` John Stultz
2013-04-08 20:19 ` John Stultz
2013-04-08 20:34 ` Prarit Bhargava
2013-04-08 20:38 ` John Stultz
2013-04-24 22:42 ` Guenter Roeck [this message]
2013-04-25 0:05 ` John Stultz
2013-04-25 0:35 ` Guenter Roeck
2013-04-25 0:43 ` John Stultz
2013-04-25 1:38 ` Li Zefan
2013-04-25 4:49 ` Guenter Roeck
2013-04-10 23:12 ` Guenter Roeck
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=20130424224218.GA7767@roeck-us.net \
--to=linux@roeck-us.net \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prarit@redhat.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.