linux-kernel - Re: [PATCH 1/2] itimers: fix racy writes to cpu

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

Message-ID: <20090930150548.GA22195@dhcp-lab-161.englab.brq.redhat.com>
Date:	Wed, 30 Sep 2009 17:05:49 +0200
From:	Stanislaw Gruszka <sgruszka@...hat.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Thomas Gleixner <tglx@...utronix.de>,
	Oleg Nesterov <oleg@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] itimers: fix racy writes to cpu_itimer fields

On Thu, Sep 24, 2009 at 10:19:43PM +0200, Ingo Molnar wrote:
> > [ there is no reason to rely on the tick though, we can program the 
> > hrtimer on sched in to expire on at the right moment, and do so on 
> > each schedule for as long as an itimer is active - re-setting whatever 
> > pending timer the cpu still had. ]
> 
> we should think about the simplest approach: switching itimers to 
> hrtimers.

I agree we need better implementation of posix-cpu-timers, however as
far we have this not perfect code and two patches fix bugs on it.
Not critical bugs, but I think they should be applied. Have I resend
them ?

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