linux-kernel - Re: [PATCH] usb/gadget: initialize gadget functions helper befor functions & gadgets

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]

Message-ID: <20130305191840.GB18329@kibibi>
Date:	Tue, 5 Mar 2013 20:18:40 +0100
From:	Sebastian Andrzej Siewior <sebastian@...akpoint.cc>
To:	Fengguang Wu <fengguang.wu@...el.com>
Cc:	linux-usb@...r.kernel.org, Felipe Balbi <balbi@...com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] usb/gadget: initialize gadget functions helper befor
 functions & gadgets

* Fengguang Wu | 2013-03-05 18:35:13 [+0800]:

>Note that I still get this warning, however looks like an unrelated
>issue:
>
>[  602.536679] [ INFO: possible circular locking dependency detected ]
>[  602.536672] 
>[  602.536679] ======================================================
>[  602.536679] [ INFO: possible circular locking dependency detected ]
>[  602.536693] 3.8.0-bisect-next-20130301-dirty #212 Not tainted
>[  602.536694] -------------------------------------------------------
>[  602.536698] kworker/0:1/27 is trying to acquire lock:
>[  602.536750]  (&fb_info->lock){+.+.+.}, at: [<ffffffff814c0176>] lock_fb_info+0x26/0x60
>[  602.536751] 
>[  602.536751] but task is already holding lock:
>[  602.536773]  (console_lock){+.+.+.}, at: [<ffffffff815a6a13>] console_callback+0x13/0x150
>[  602.536774]                 
>[  602.536774] which lock already depends on the new lock.

This does not look good but it does not like USB. It looks more like the
tty/fb area.

>Thanks,
>Fengguang

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