linux-kernel - Re: [usb gadget] WARNING: at kernel/mutex.c:198 __mutex_lock

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: <20130302134536.GA16893@localhost>
Date:	Sat, 2 Mar 2013 21:45:36 +0800
From:	Fengguang Wu <fengguang.wu@...el.com>
To:	Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc:	Felipe Balbi <balbi@...com>,
	Maarten Lankhorst <m.b.lankhorst@...il.com>,
	linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [usb gadget] WARNING: at kernel/mutex.c:198 __mutex_lock_common()

On Sat, Mar 02, 2013 at 02:41:07PM +0100, Sebastian Andrzej Siewior wrote:
> On 03/02/2013 02:37 PM, Fengguang Wu wrote:
> > On Wed, Feb 27, 2013 at 12:49:35PM +0200, Felipe Balbi wrote:
> >> Hi,
> >>
> >> On Wed, Feb 06, 2013 at 10:04:24AM +0800, Fengguang Wu wrote:
> >>> Greetings,
> >>>
> >>> I got the below warning and the first bad commit is
> >>
> >> can you send a fixup patch ?
> > 
> > Sorry I don't have the fix. Maarten once proposed
> > 
> > : Can you change __mutex_lock_common from inline to __always_inline and
> > : check if that gets rid of the warning?
> > 
> > and it worked at that time, however it does not work today when I
> > go out to double check the below patch...
> 
> This does not get even close to a fix, not to mention a proper one. The
> problem is that a spinlock is hold while a mutex is going to be taken.
> Maybe I get to this?

That'd be great. I can help test your patch out.

Thanks,
Fengguang
--
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/