From: Brian King <brking@linux.vnet.ibm.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: mingo@elte.hu, efault@gmx.de, vatsa@in.ibm.com,
balbir@linux.vnet.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] sched: CPU remove deadlock fix
Date: Tue, 09 Dec 2008 09:07:25 -0600 [thread overview]
Message-ID: <493E89AD.8000106@linux.vnet.ibm.com> (raw)
In-Reply-To: <1228834342.8684.5.camel@twins>
Peter Zijlstra wrote:
> On Tue, 2008-12-09 at 08:47 -0600, Brian King wrote:
>> This patch fixes a possible deadlock scenario in the CPU remove path.
>> migration_call grabs rq->lock, then wakes up everything on rq->migration_queue
>> with the lock held. Then one of the tasks on the migration queue ends up
>> calling tg_shares_up which then also tries to acquire the same rq->lock.
>
> Looks ok, does lockdep agree?
I didn't have lockdep enabled when I verified it, but the section of code now
looks like:
spin_lock_irq(&rq->lock);
while (!list_empty(&rq->migration_queue)) {
struct migration_req *req;
req = list_entry(rq->migration_queue.next,
struct migration_req, list);
list_del_init(&req->list);
spin_unlock_irq(&rq->lock);
complete(&req->done);
spin_lock_irq(&rq->lock);
}
spin_unlock_irq(&rq->lock);
So I'm pretty sure lockdep will agree.
-Brian
>
>> Signed-off-by: Brian King <brking@linux.vnet.ibm.com>
>> ---
>>
>> kernel/sched.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff -puN kernel/sched.c~sched_cpu_down_deadlock_fix kernel/sched.c
>> --- linux-2.6/kernel/sched.c~sched_cpu_down_deadlock_fix 2008-12-09 08:42:09.000000000 -0600
>> +++ linux-2.6-bjking1/kernel/sched.c 2008-12-09 08:42:09.000000000 -0600
>> @@ -6587,7 +6587,9 @@ migration_call(struct notifier_block *nf
>> req = list_entry(rq->migration_queue.next,
>> struct migration_req, list);
>> list_del_init(&req->list);
>> + spin_unlock_irq(&rq->lock);
>> complete(&req->done);
>> + spin_lock_irq(&rq->lock);
>> }
>> spin_unlock_irq(&rq->lock);
>> break;
>> _
>
--
Brian King
Linux on Power Virtualization
IBM Linux Technology Center
next prev parent reply other threads:[~2008-12-09 15:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-09 14:47 [PATCH 1/1] sched: CPU remove deadlock fix Brian King
2008-12-09 14:52 ` Peter Zijlstra
2008-12-09 14:59 ` Peter Zijlstra
2008-12-09 15:11 ` Peter Zijlstra
2008-12-09 15:14 ` Brian King
2008-12-09 15:07 ` Brian King [this message]
2008-12-09 18:12 ` Heiko Carstens
2008-12-09 18:27 ` Ingo Molnar
2008-12-09 18:27 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=493E89AD.8000106@linux.vnet.ibm.com \
--to=brking@linux.vnet.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=balbir@linux.vnet.ibm.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=vatsa@in.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.