Date: Tue, 22 Jan 2008 18:07:00 +0100
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
Message-ID: <20080122170700.GA6245@elte.hu>
References: <20080122023626.GA12213@darkstar.te-china.tietoenator.com> <1201019138.6341.24.camel@lappy>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1201019138.6341.24.camel@lappy>
User-Agent: Mutt/1.5.17 (2007-11-01)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 652
Lines: 19


* 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/