linux-kernel - Re: (BUG?) round_jiffies() is non-monotonic on SMP

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]

Date:	Sat, 1 Nov 2008 13:16:48 -0700
From:	Arjan van de Ven <arjan@...radead.org>
To:	Alan Stern <stern@...land.harvard.edu>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...hat.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Kernel development list <linux-kernel@...r.kernel.org>
Subject: Re: (BUG?) round_jiffies() is non-monotonic on SMP

On Sat, 1 Nov 2008 15:54:16 -0400 (EDT)
Alan Stern <stern@...land.harvard.edu> wrote:

> On Sat, 1 Nov 2008, Arjan van de Ven wrote:
> 
> > > If this is known, is it regarded as a potential problem?  It
> > > certainly seems likely that some code somewhere depends on
> > > timeouts expiring in the correct order.
> > 
> > I don't think timeouts EVER have that guarantee between different
> > cpus; even if you don't round the timeouts.
> > After all, your CPU A can be in some delay loop with irqs off for
> > longer than the delta was, and boom.. the timers fire in different
> > order.
> 
> Why is that?  The fact that CPU A is busy might mean that the timer
> routines run on some other CPU... but they should still be called in
> the correct order.

Hi,

I think you misunderstand how timers work right now ;)

timers are a per cpu list, and each cpu has its own interrupt to
service this per cpu list.

now... if one cpu disables interrupts for a while, that cpus interrupts
get blocked, including that cpus timer handling irq (whichever method
is used for that)... and only that cpus timers will get delayed, the
other cpus will just keep rolling...


> 
> Is it possible for timer 1 to expire before timer 2 but the handler
> gets interrupted, with the result that timer 2's handler runs to
> completion on a different CPU before timer 1's handler has managed to
> execute more than a couple of instructions?  If it is then I agree,
> timer-ordering requirements between CPUs don't make much sense.

yes
> 
> 
> Come to think of it, is there any good reason why round_jiffies()  
> doesn't always round up?  It seems a lot safer.

at the time folks had concerns about making a big error in that
direction...


-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
--
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/