linux-kernel - Re: rt-kernel 3.0.14-rt31: BUG: sleeping function called from invalid 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]

Message-Id: <201201180053.52617.fzuuzf@googlemail.com>
Date:	Wed, 18 Jan 2012 00:53:51 +0100
From:	Karsten Wiese <fzuuzf@...glemail.com>
To:	John Kacur <jkacur@...hat.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	RT <linux-rt-users@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Steven Rostedt <rostedt@...dmis.org>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	Peter Zijlstra <peterz@...radead.org>
Subject: Re: rt-kernel 3.0.14-rt31: BUG: sleeping function called from invalid context

Am Mittwoch 18 Januar 2012 schrieb John Kacur:
> I got a whole bunch of these in 3.0.14-rt31 that basically look alike.
> Will try to drill deeper down. In the meantime, I'm happy to provide
> more information if anyone would like.
> Thanks, John
> 
> [ 4251.928097] BUG: sleeping function called from invalid context at
> /home/jkacur/rt.linux.git/kernel/rtmutex.c:645
> [ 4251.928100] in_atomic(): 1, irqs_disabled(): 1, pid: 168, name: irq/9-acpi
> [ 4251.928102] INFO: lockdep is turned off.
> [ 4251.928103] irq event stamp: 5888
> [ 4251.928104] hardirqs last  enabled at (5887): [<ffffffff810b2a69>]
> rcu_preempt_note_context_switch+0x1c8/0x1d9
> [ 4251.928109] hardirqs last disabled at (5888): [<ffffffff813e4326>]
> _raw_spin_lock_irq+0x19/0x79
> [ 4251.928113] softirqs last  enabled at (0): [<ffffffff81041c88>]
> copy_process+0x517/0xfbd
> [ 4251.928116] softirqs last disabled at (0): [<          (null)>]
>       (null)
> [ 4251.928119] Pid: 168, comm: irq/9-acpi Not tainted
> 3.0.14-rt31-debug-00322-g6aaac97b #1
> [ 4251.928121] Call Trace:
> [ 4251.928125]  [<ffffffff81037b06>] __might_sleep+0xf4/0xf9
> [ 4251.928128]  [<ffffffff8107e4f5>] rt_spin_lock_fastlock.clone.0+0x24/0x31
> [ 4251.928130]  [<ffffffff813e3b33>] rt_spin_lock+0x16/0x40
> [ 4251.928133]  [<ffffffff8103eb60>] __wake_up+0x28/0x50
> [ 4251.928136]  [<ffffffff8122ca51>] acpi_ec_gpe_handler+0x72/0xc4
> [ 4251.928145]  [<ffffffff81238443>] acpi_ev_gpe_dispatch+0xbd/0x12e
> [ 4251.928147]  [<ffffffff81238727>] acpi_ev_gpe_detect+0xbb/0x110

The bug happens because acpi_ev_gpe_detect does
raw_spin_lock_irqsave(&acpi_gbl_gpe_lock, flags) before it calls
acpi_ev_gpe_dispatch.
--
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/