linux-kernel - Re: mmotm 2010-09-15 - BUG in mmc driver calling led_trigger

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:	Wed, 22 Sep 2010 04:14:53 +0100
From:	Chris Ball <cjb@...top.org>
To:	Valdis.Kletnieks@...edu
Cc:	akpm@...ux-foundation.org, Richard Purdie <rpurdie@...ys.net>,
	Hein_Tibosch <hein_tibosch@...oo.es>,
	linux-kernel@...r.kernel.org, linux-mmc@...r.kernel.org
Subject: Re: mmotm 2010-09-15 - BUG in mmc driver calling
	led_trigger_event()

Hi Valdis,

On Tue, Sep 21, 2010 at 11:01:47PM -0400, Valdis.Kletnieks@...edu wrote:
> [    2.934051] BUG: sleeping function called from invalid context at kernel/mutex.c:278
> [    2.934440] in_atomic(): 1, irqs_disabled(): 0, pid: 11, name: kworker/0:1
>
> [...]
> 
> Anything obvious to you guys? Race condition of some sort, or somebody
> else leaving a dangling in_atomic() status for us to get ambushed by?
> Maybe Hein's patches to retry at multiple freqs are causing one of the
> retries to happen at a bad time? I'm mystified.

This is caused by Anton Vorontsov's patchset here:
   http://lkml.org/lkml/2010/7/14/127

I reported the same symptom:
   http://lkml.org/lkml/2010/9/8/435

and suggested that Andrew remove the patchset from -mm while we work out
the bugs.

Thanks,

-- 
Chris Ball   <cjb@...top.org>   <http://printf.net/>
One Laptop Per Child
--
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/