From: Ingo Molnar <mingo@elte.hu>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Dave Young <hidave.darkstar@gmail.com>,
linux-kernel@vger.kernel.org,
Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>
Subject: Re: [PATCH] sched: don't take a mutex from interrupt context
Date: Tue, 22 Jan 2008 18:07:00 +0100 [thread overview]
Message-ID: <20080122170700.GA6245@elte.hu> (raw)
In-Reply-To: <1201019138.6341.24.camel@lappy>
* Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
> > WARNING: at kernel/mutex.c:134 mutex_lock_nested+0x277/0x290()
> Subject: sched: don't take a mutex from interrupt context
>
> print_cfs_stats is callable from interrupt context (sysrq), hence it
> should not take mutexes. Change it to use RCU since the task group
> data is RCU freed anyway.
thanks Peter, applied this to sched-devel.git.
Ingo
prev parent reply other threads:[~2008-01-22 17:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-22 2:36 WARNING: at kernel/mutex.c:134 Dave Young
2008-01-22 16:25 ` [PATCH] sched: don't take a mutex from interrupt context Peter Zijlstra
2008-01-22 16:51 ` Srivatsa Vaddagiri
2008-01-22 16:47 ` Peter Zijlstra
2008-01-22 17:23 ` Srivatsa Vaddagiri
2008-01-22 17:07 ` Ingo Molnar [this message]
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=20080122170700.GA6245@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=hidave.darkstar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vatsa@linux.vnet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).