linux-kernel - Re: [stable 2.6.24] WARNING: at kernel/time/clockevents.c

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <200802141230.14625.elendil@planet.nl>
Date:	Thu, 14 Feb 2008 12:30:13 +0100
From:	Frans Pop <elendil@...net.nl>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, john stultz <johnstul@...ibm.com>
Subject: Re: [stable 2.6.24] WARNING: at kernel/time/clockevents.c

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
--
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/