linux-kernel - Re: 'global' rq->clock

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 for Android: free password hash cracker in your pocket

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

Message-Id: <1209853855.26383.28.camel@pasglop>
Date:	Sun, 04 May 2008 08:30:55 +1000
From:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
To:	David Miller <davem@...emloft.net>
Cc:	mingo@...e.hu, a.p.zijlstra@...llo.nl, efault@....de,
	elendil@...net.nl, parag.warudkar@...il.com,
	linux-kernel@...r.kernel.org, guichaz@...oo.fr, andi@...stfloor.org
Subject: Re: 'global' rq->clock


On Sat, 2008-05-03 at 12:27 -0700, David Miller wrote:
> > ( although please note that the growing generalization that goes on
> >   _did_ find a subtle nohz problem on sparc64 early in the merge
> window,
> >   so it's not like these changes are totally useless to you. )
> 
> Note that this bug theoretically exists on every platform,
> even x86, and only sparc64 is fixed at the moment by adding
> the irq_{entry,exit}() guards around all of it's IPI handlers.

What is the bug ?

IPIs on power are normal interrupts, so they do happen in irq_entry/exit
blocks but I'm curious to know what the root bug is :-)

Ben.


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