linux-kernel - Re: [PATCH v3 tip/core/rcu 3/9] rcu: Add synchronous grace-period waiting for RCU-tasks

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: <20140802225857.GC8101@linux.vnet.ibm.com>
Date:	Sat, 2 Aug 2014 15:58:57 -0700
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	Oleg Nesterov <oleg@...hat.com>
Cc:	linux-kernel@...r.kernel.org, mingo@...nel.org,
	laijs@...fujitsu.com, dipankar@...ibm.com,
	akpm@...ux-foundation.org, mathieu.desnoyers@...icios.com,
	josh@...htriplett.org, tglx@...utronix.de, peterz@...radead.org,
	rostedt@...dmis.org, dhowells@...hat.com, edumazet@...gle.com,
	dvhart@...ux.intel.com, fweisbec@...il.com, bobby.prani@...il.com
Subject: Re: [PATCH v3 tip/core/rcu 3/9] rcu: Add synchronous grace-period
 waiting for RCU-tasks

On Sat, Aug 02, 2014 at 04:47:19PM +0200, Oleg Nesterov wrote:
> On 08/01, Paul E. McKenney wrote:
> >
> > On Fri, Aug 01, 2014 at 11:32:51AM -0700, Paul E. McKenney wrote:
> > > On Fri, Aug 01, 2014 at 05:09:26PM +0200, Oleg Nesterov wrote:
> > > > On 07/31, Paul E. McKenney wrote:
> > > > >
> > > > > +void synchronize_rcu_tasks(void)
> > > > > +{
> > > > > +	/* Complain if the scheduler has not started.  */
> > > > > +	rcu_lockdep_assert(!rcu_scheduler_active,
> > > > > +			   "synchronize_rcu_tasks called too soon");
> > > > > +
> > > > > +	/* Wait for the grace period. */
> > > > > +	wait_rcu_gp(call_rcu_tasks);
> > > > > +}
> > > >
> > > > Btw, what about CONFIG_PREEMPT=n ?
> > > >
> > > > I mean, can't synchronize_rcu_tasks() be synchronize_sched() in this
> > > > case?
> > >
> > > Excellent point, indeed it can!
> > >
> > > And if I do it right, it will make CONFIG_TASKS_RCU=y safe for kernel
> > > tinification.  ;-)
> >
> > Unless, that is, we need to wait for trampolines in the idle loop...
> >
> > Sounds like a question for Steven.  ;-)
> 
> Sure, but the full blown synchronize_rcu_tasks() can't handle the idle threads
> anyway. An idle thread can not be deactivated and for_each_process() can't see
> it anyway.

Indeed, if idle threads need to be tracked, their tracking will need to
be at least partially special-cased.

							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/