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: <20110711160330.GC4109@somewhere.redhat.com>
Date:	Mon, 11 Jul 2011 18:03:32 +0200
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Cc:	linux-kernel@...r.kernel.org, mingo@...e.hu, laijs@...fujitsu.com,
	dipankar@...ibm.com, akpm@...ux-foundation.org,
	mathieu.desnoyers@...ymtl.ca, josh@...htriplett.org,
	niv@...ibm.com, tglx@...utronix.de, peterz@...radead.org,
	rostedt@...dmis.org, Valdis.Kletnieks@...edu, dhowells@...hat.com,
	eric.dumazet@...il.com, darren@...art.com, patches@...aro.org
Subject: Re: [PATCH tip/core/rcu 0/6] Check for use of RCU from dyntick-idle
 mode

On Fri, Jul 08, 2011 at 08:43:31AM -0700, Paul E. McKenney wrote:
> Hello!
> 
> This set of patches adds checks for use of RCU from "extended quiescent
> states" such as dyntick-idle mode.  Such use is grossly illegal because
> RCU by definition ignores CPUs that are in extended quiescent states.
> In the case of dyntick-idle mode, the only way for RCU to avoid ignoring
> such CPUs would be to wake them up periodically, which would defeat the
> whole purpose of dyntick-idle mode.
> 
> The good news is that Frederic got this effort started.  The bad news is
> that there are several cases where RCU read-side critical sections appear
> in dyntick-idle mode.

Ok, let me send to you the patch that splits up rcu/tickless logic and I'll try
to fix up what you reported to me in ppc.

BTW, are you aware of other cases? You mentioned "several" :)
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ