Re: [PATCH] generic-ipi: fix deadlock in __smp_call_function_single

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Venkatesh Pallipadi
Date: Saturday, September 11, 2010 - 9:42 am

On Sat, Sep 11, 2010 at 2:20 AM, Peter Zijlstra <peterz@infradead.org> wrote:

Yes. This was an oversight while moving from using send_remote_softirq
to using __smp_call_function_single.
Also, as we don't have rq lock around this point, it seems possible
that the CPU that was busy and wants to kick idle load balance on
remote CPU, could have become idle and nominated itself as idle load
balancer.

Below patch looks good to me.

Acked-by: Venkatesh Pallipadi <venki@google.com>

I guess, we also need a WARN_ON_ONCE for (cpu == smp_processor_id())
in __smp_call_function_single(), as the eventual result of this bug
that Heiko saw was a deadlock

Thanks,
Venki

--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[tip:core/urgent] generic-ipi: Fix deadlock in __smp_call_ ..., tip-bot for Heiko Ca ..., (Fri Sep 10, 8:47 am)
Re: [PATCH] generic-ipi: fix deadlock in __smp_call_functi ..., Venkatesh Pallipadi, (Sat Sep 11, 9:42 am)
[tip:sched/urgent] sched: Fix nohz balance kick, tip-bot for Suresh S ..., (Tue Sep 21, 7:13 am)