linux-kernel - Re: [PATCH] hres_timers_resume must block interrupts

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]

Date:	Tue, 14 Aug 2007 08:27:36 +0200
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Joe Korty <joe.korty@...r.com>
Cc:	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] hres_timers_resume must block interrupts

On Tue, 2007-08-14 at 07:36 +0200, Thomas Gleixner wrote:
> On Mon, 2007-08-13 at 19:26 -0400, Joe Korty wrote:
> > Retrigger_next_event() must be called with interrupts disabled.
> > 
> > All internal (to hrtimer.c) uses of retrigger_next_event() are correct.
> > But the version exported to other files, hres_timers_resume(), does not
> > do the IRQ blocking, nor does the (single) external caller of it.
> > 
> > Rather than require that users of hres_timers_resume() do the IRQ blocking,
> > this patch makes the blocking part of the hres_timers_resume() functionality.
> 
> Ack.

-ENOTENOUGHCOFFEE. 

The resume functions are called with interrupts disabled. Nothing to fix
here.

	tglx


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