linux-kernel - Re: [PATCH 05/32] nohz: Move rcu dynticks idle mode handling to idle enter/exit APIs

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: <1314718952.5812.23.camel@twins>
Date:	Tue, 30 Aug 2011 17:42:32 +0200
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Anton Blanchard <anton@....ibm.com>,
	Avi Kivity <avi@...hat.com>, Ingo Molnar <mingo@...e.hu>,
	Lai Jiangshan <laijs@...fujitsu.com>,
	"Paul E . McKenney" <paulmck@...ux.vnet.ibm.com>,
	Stephen Hemminger <shemminger@...tta.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Tim Pepper <lnxninja@...ux.vnet.ibm.com>,
	Paul Menage <paul@...lmenage.org>
Subject: Re: [PATCH 05/32] nohz: Move rcu dynticks idle mode handling to
 idle enter/exit APIs

On Tue, 2011-08-30 at 17:33 +0200, Frederic Weisbecker wrote:
> > See all that is still kernelspace ;-) I think I know what you mean to
> > say though, but seeing as you note there is even now a known shortcoming
> > I'm not very confident its a solid construction. What will help us find
> > such holes?
> 
> This: https://lkml.org/lkml/2011/6/23/744
> 
> It's in one of Paul's branches and should make it for the next merge window.
> This should detect any of such holes. I made that on purpose for the nohz cpusets
> when I saw how much error prone that can be with rcu :)

OK, good ;-)

> > I would much rather we not rely on such fragile things too much.. this
> > RCU stuff wants way more thought, as it stands your patch-set doesn't do
> > anything useful IMO.
> 
> Not sure what you mean. Well that Rcu thing for sure is fragile but we have
> the tools ready to find the problems. 

Right that thing you linked above does catch abuse, still your current
proposal means that due to RCU it will basically never disable the tick.
--
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/