linux-kernel - Re: BUG: sleeping function called from invalid context at kernel/mutex.c:271

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, 18 Apr 2012 22:19:55 +0600
From:	"Alexander E. Patrakov" <patrakov@...il.com>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	paulmck@...ux.vnet.ibm.com, linux-kernel@...r.kernel.org
Subject: Re: BUG: sleeping function called from invalid context at
 kernel/mutex.c:271

I wrote:
> Steven Rostedt wrote:
> > On Wed, 2012-04-18 at 19:45 +0600, Alexander E. Patrakov wrote:
> > 
> > > > Do you see the RT throttling message too? That's a bug with an RT task
> > > > going haywire. If that is happening, an RT task may be preventing an RCU
> > > > grace period to finish, and causing the RCU stalls.
> > > 
> > > I am currently at home, writing this from a laptop with 3.3.1, and there
> > 
> > Have you seen the memory leaks on your laptop?
> > 
> > > are no such messages in dmesg (yet?). Also I don't know any RT tasks
> > > that may run on my computer, except pulseaudio, which has a built-in
> > 
> > There are kernel threads that run at RT priorities too.
> > 
> > > safeguard against this. As for the work computer, should I check
> > > tomorrow, and with which kernel version?
> > > 
> > 
> > I'm only interested in the kernel version that happens to leak. If other
> > versions don't leak then we don't need to worry about them ;-)
> 
> Attached is a config and a full dmesg on 3.3.0 on the laptop. No obvious
> memory leak - but this may be just the beginning, as the laptop still
> responds well enough for me to send this email.

Given how short the time to trigger the BUG was on the laptop, the fact
that it mentioned ipv6 in the trace and that the BUG is not triggered
yet on 3.3.0 + 731184bff, I am confident that the BUG is dead now. Fixed
by 731184bff, which is in 3.3.1.

-- 
Alexander E. Patrakov

--
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/