Re: 3.9.x: Possible race related to stop_machine leads to lockup.

2013-06-05 Thread Ben Greear
On 06/04/2013 09:41 PM, Rusty Russell wrote: Ben Greear writes: On 06/04/2013 02:18 PM, Ben Greear wrote: I've been trying to figure out why I see the migration/* processes hang in a busy loop While reading the stop_machine.c file, I think I might have an answer. The set_state() method s

Re: 3.9.x: Possible race related to stop_machine leads to lockup.

2013-06-04 Thread Rusty Russell
Ben Greear writes: > On 06/04/2013 02:18 PM, Ben Greear wrote: >> I've been trying to figure out why I see the migration/* processes >> hang in a busy loop >> >> While reading the stop_machine.c file, I think I might have an >> answer. >> >> The set_state() method sets the thread_ack to the cu

Re: 3.9.x: Possible race related to stop_machine leads to lockup.

2013-06-04 Thread Ben Greear
On 06/04/2013 02:18 PM, Ben Greear wrote: I've been trying to figure out why I see the migration/* processes hang in a busy loop While reading the stop_machine.c file, I think I might have an answer. The set_state() method sets the thread_ack to the current number of threads. Each thread's

3.9.x: Possible race related to stop_machine leads to lockup.

2013-06-04 Thread Ben Greear
I've been trying to figure out why I see the migration/* processes hang in a busy loop While reading the stop_machine.c file, I think I might have an answer. The set_state() method sets the thread_ack to the current number of threads. Each thread's state machine then decrements it down to z