linux-kernel - Re: lots of suspicious RCU traces

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]

Date:	Wed, 24 Oct 2012 13:15:39 -0700
From:	Sergey Senozhatsky <sergey.senozhatsky@...il.com>
To:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Cc:	Oleg Nesterov <oleg@...hat.com>, Dave Jones <davej@...hat.com>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Serge Hallyn <serge.hallyn@...onical.com>,
	linux-kernel@...r.kernel.org
Subject: Re: lots of suspicious RCU traces

On (10/24/12 13:11), Paul E. McKenney wrote:
> > > > 
> > > > sorry, I meant idle from RCU point of view:
> > > > 
> > > > int rcu_is_cpu_idle(void)
> > > > {
> > > >          return !rcu_dynticks_nesting;
> > > > }
> > > 
> > > Hmmm...  This reproduces on UP builds, then?
> > 
> > I'll compile UP build (will offlining of N-1 CPUs do the trick?).
> 
> Oh -- you quoted the Tiny RCU (CONFIG_SMP=n) variant of rcu_is_cpu_idle(),

sorry, that was just an 'illustration'.

	-ss

> so I just thought that you were reproducing on CONFIG_SMP=n.  You would
> have to actually rebuild the kernel to get the different version.
> 
> But never mind!  RCU_USER_QS depends on CONFIG_SMP=y, so my question
> was irrelevant.
> 
> 							Thanx, Paul
> 
--
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/