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] [day] [month] [year] [list]

Date:	Wed, 25 Jan 2012 12:02:19 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	John Kacur <jkacur@...hat.com>
cc:	Steven Rostedt <rostedt@...dmis.org>,
	Karsten Wiese <fzuuzf@...glemail.com>,
	LKML <linux-kernel@...r.kernel.org>,
	RT <linux-rt-users@...r.kernel.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

On Thu, 19 Jan 2012, John Kacur wrote:

> On Thu, Jan 19, 2012 at 5:38 PM, Steven Rostedt <rostedt@...dmis.org> wrote:
> > On Thu, 2012-01-19 at 17:16 +0100, John Kacur wrote:
> > 
> >> I'm testing v3.0.14-rt32-rc1, and it greatly reduced the number of
> >> these, but I still got one during boot.
> >>
> >> [   11.938649] BUG: sleeping function called from invalid context at
> >> /home/jkacur/rt.linux.git/kernel/rtmutex.c:645
> >> [   11.938651] in_atomic(): 1, irqs_disabled(): 1, pid: 168, name: irq/9-acpi
> >> [   11.938653] 1 lock held by irq/9-acpi/168:
> >> [   11.938653]  #0:  (acpi_gbl_gpe_lock){......}, at:
> >> [<ffffffff8123881d>] acpi_ev_gpe_detect+0x31/0x110
> >
> > Could you test 3.2-rt. If that has the issue then we know we have more
> > to fix. If not, we know I missed a patch.
> >
> 
> I tested with v3.2-rt10 and the issue is not there.

I'm surprised. I know already what the problem is and according to the
code it should be visible in 3.2 as well. I'm still twisting my head
around that acpi maze to fix that particular one.

> I also examined your patches and couldn't find anything wrong with
> them, and for larks tried applying
> cpumask-disable-offstack-on-rt.patch from v3.2-rt10
> all to no avail, the problem is still there.

What a surprise, it's completely unrelated.