linux-kernel - Re: CPU used at 100% in 2.6.39-git10

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>] [day] [month] [year] [list]

Date:	Thu, 26 May 2011 01:08:04 +0300
From:	Anca Emanuel <anca.emanuel@...il.com>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andi Kleen <ak@...ux.intel.com>,
	Peter Zijlstra <peterz@...radead.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: CPU used at 100% in 2.6.39-git10

On Thu, May 26, 2011 at 12:08 AM, Thomas Gleixner <tglx@...utronix.de> wrote:
> On Wed, 25 May 2011, Linus Torvalds wrote:
>
>> On Wed, May 25, 2011 at 1:37 PM, Thomas Gleixner <tglx@...utronix.de> wrote:
>> >
>> > /me blushes
>> >
>> > Does the patch below fix it ?
>>
>> Yup, that seems to fix it for me. Commit log and sign-off?
>>
>>                         Linus
>
> ---->
> hrtimers: Fix moronic typo
>
> commit 9ec2690758a5 ("timerfd: Manage cancelable timers in timerfd")
> introduced a CONFIG_HIGHRES_TIMERS (should be CONFIG_HIGH_RES_TIMERS)
> typo, which caused applications depending on CLOCK_REALTIME timers to
> become sluggy due to the fact that the time base of the realtime
> timers was not updated when the wall clock time was set.
>
> Reported-by: Anca Emanuel <anca.emanuel@...il.com>
> Fatfingered-by: Thomas Gleixner <tglx@...utronix.de>
> Signed-off-by: Thomas Gleixner <tglx@...utronix.de>
>
> diff --git a/kernel/hrtimer.c b/kernel/hrtimer.c
> index c541ee5..a9205e3 100644
> --- a/kernel/hrtimer.c
> +++ b/kernel/hrtimer.c
> @@ -748,7 +748,7 @@ static inline void retrigger_next_event(void *arg) { }
>  */
>  void clock_was_set(void)
>  {
> -#ifdef CONFIG_HIGHRES_TIMERS
> +#ifdef CONFIG_HIGH_RES_TIMERS
>        /* Retrigger the CPU local events everywhere */
>        on_each_cpu(retrigger_next_event, NULL, 1);
>  #endif
>

Tested-by: Anca Emanuel <anca.emanuel@...il.com>

Linus, Thomas, this solves the problem, thanks very much for your help.
--
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/