[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1250533487.2709.14.camel@josh-work.beaverton.ibm.com>
Date: Mon, 17 Aug 2009 11:24:47 -0700
From: Josh Triplett <josht@...ux.vnet.ibm.com>
To: 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, dvhltc@...ibm.com, niv@...ibm.com,
tglx@...utronix.de, peterz@...radead.org, rostedt@...dmis.org,
hugh.dickins@...cali.co.uk, benh@...nel.crashing.org
Subject: Re: [PATCH -tip/core/rcu 1/6] Cleanups and fixes for RCU in face
of heavy CPU-hotplug stress
On Sat, 2009-08-15 at 09:51 -0700, Paul E. McKenney wrote:
> These pass tests combining rcutorture and continuous CPU-hotplug
> operations, in other words, no sleeping between successive CPU-hotplug
> operations. This set does not fix the bug involving deadlocks through
> rcutorture, kthread_stop(), and migration threads. However, this bug
> does not affect production systems, so should not stand in the way of
> applying these patches.
Commit 63706172f332fd3f6e7458ebfb35fa6de9c21dc5, "kthreads: rework
kthread_stop()", looks like it fixes kthread_stop to work concurrently.
That may fix the issue you observed.
- Josh Triplett
--
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