All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frans Pop <elendil@planet.nl>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, john stultz <johnstul@us.ibm.com>
Subject: Re: [stable 2.6.24] WARNING: at kernel/time/clockevents.c
Date: Thu, 14 Feb 2008 12:30:13 +0100	[thread overview]
Message-ID: <200802141230.14625.elendil@planet.nl> (raw)
In-Reply-To: <alpine.LFD.1.00.0802140029550.12988@apollo.tec.linutronix.de>

On Thursday 14 February 2008, Thomas Gleixner wrote:
> futex_lock_pi is called with an absolute timeout, which is based on
> CLOCK_REALTIME. Nothing wrong with that, but the clockevents WARN_ON
> might trap over a false positive, when the expiry value is less than
> base->offset. This was intentional before we put the WARN_ON into the
> clockevents code.
>
> The patch below should fix this issue.

With these two patches on top of 2.6.24.2 I no longer get any warnings 
during a glibc compile:
- hrtimer: check relative timeouts for overflow
- hrtimer: fix abs clock realtime

Thanks Thomas.

Cheers,
FJP

      reply	other threads:[~2008-02-14 11:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-10 13:40 [stable 2.6.24] WARNING: at kernel/time/clockevents.c Frans Pop
2008-02-10 14:20 ` Frans Pop
2008-02-13  7:07 ` Andrew Morton
2008-02-13  8:21   ` Thomas Gleixner
2008-02-13  8:47     ` Frans Pop
2008-02-13  9:32       ` Thomas Gleixner
2008-02-13 21:40         ` Frans Pop
2008-02-14  0:20           ` Thomas Gleixner
2008-02-14 11:30             ` Frans Pop [this message]

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=200802141230.14625.elendil@planet.nl \
    --to=elendil@planet.nl \
    --cc=akpm@linux-foundation.org \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@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.