linux-kernel - Re: [PATCH] sched: don't take a mutex from interrupt context

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 22 Jan 2008 18:07:00 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc:	Dave Young <hidave.darkstar@...il.com>,
	linux-kernel@...r.kernel.org,
	Srivatsa Vaddagiri <vatsa@...ux.vnet.ibm.com>
Subject: Re: [PATCH] sched: don't take a mutex from interrupt context


* Peter Zijlstra <a.p.zijlstra@...llo.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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/