From: Greg KH <gregkh@linuxfoundation.org>
To: Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: removing usb debug cable triggers lockdep warning.
Date: Sat, 1 Feb 2014 09:45:14 +0100 [thread overview]
Message-ID: <20140201084514.GC4973@kroah.com> (raw)
In-Reply-To: <20140131211118.GA23873@redhat.com>
On Fri, Jan 31, 2014 at 04:11:18PM -0500, Dave Jones wrote:
> usb 3-3: USB disconnect, device number 2
> console [ttyUSB0] disabled
> debug ttyUSB0: debug converter now disconnected from ttyUSB0
> usb_debug 3-3:1.0: device disconnected
> INFO: trying to register non-static key.
> the code is fine but needs lockdep annotation.
> turning off the locking correctness validator.
> CPU: 3 PID: 66 Comm: khubd Not tainted 3.13.0+ #104
> ffffffffbb28cf50 000000000f74f0eb ffff880242eb3a08 ffffffffba73a377
> ffff880243741740 ffff880242eb3a18 ffffffffba7368b9 ffff880242eb3a90
> ffffffffba0c1560 0000000000000003 ffff880242eb2000 ffff880242eb3aa8
> Call Trace:
> [<ffffffffba73a377>] dump_stack+0x4e/0x7a
> [<ffffffffba7368b9>] register_lock_class.part.21+0x38/0x3c
> [<ffffffffba0c1560>] __lock_acquire.isra.28+0xa10/0xa50
> [<ffffffffba0c1cfd>] lock_acquire+0x8d/0x120
> [<ffffffffba24ba88>] ? kernfs_addrm_finish+0x38/0x60
> [<ffffffffba24acde>] kernfs_deactivate+0x10e/0x150
> [<ffffffffba24ba88>] ? kernfs_addrm_finish+0x38/0x60
> [<ffffffffba24ba88>] kernfs_addrm_finish+0x38/0x60
> [<ffffffffba24bd00>] kernfs_remove_by_name_ns+0x60/0xc0
> [<ffffffffba2498d1>] remove_files.isra.1+0x41/0x80
> [<ffffffffba249bc7>] sysfs_remove_group+0x47/0xa0
> [<ffffffffba249cf3>] sysfs_remove_groups+0x33/0x50
> [<ffffffffba4ded6d>] device_remove_attrs+0x4d/0x80
> [<ffffffffba4df9ae>] device_del+0x12e/0x1d0
> [<ffffffffba53ce08>] usb_disconnect+0x138/0x1d0
> [<ffffffffba540153>] hub_thread+0x723/0x1700
> [<ffffffffba09d7c4>] ? finish_task_switch+0x44/0x190
> [<ffffffffba0ba030>] ? wake_up_atomic_t+0x30/0x30
> [<ffffffffba53fa30>] ? usb_reset_device+0x1d0/0x1d0
> [<ffffffffba093dcc>] kthread+0xfc/0x120
> [<ffffffffba093cd0>] ? kthread_create_on_node+0x230/0x230
> [<ffffffffba74d96c>] ret_from_fork+0x7c/0xb0
> [<ffffffffba093cd0>] ? kthread_create_on_node+0x230/0x230
Yeah, I have a patch from Tejun to queue up after 3.14-rc1 is out to fix
this issue, sorry for the noise.
greg k-h
prev parent reply other threads:[~2014-02-01 8:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 21:11 removing usb debug cable triggers lockdep warning Dave Jones
2014-02-01 8:45 ` Greg KH [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140201084514.GC4973@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.