From: Jiri Slaby <jirislaby@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Greg KH <gregkh@suse.de>,
linux-usb@vger.kernel.org
Subject: usb unbind/bind => WARNING at fs/sysfs/dir.c [Was: 2.6.25-rc8-mm1]
Date: Fri, 04 Apr 2008 22:16:32 +0200 [thread overview]
Message-ID: <47F68CA0.7090007@gmail.com> (raw)
In-Reply-To: <20080401213214.8fbb6d6b.akpm@linux-foundation.org>
On 04/02/2008 06:32 AM, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.25-rc8/2.6.25-rc8-mm1/
After
$ echo -n 4-1.2 >/sys/bus/usb/drivers/usb/unbind
$ echo -n 4-1.2 >/sys/bus/usb/drivers/usb/bind
I have this in logs:
sysfs: duplicate filename 'usbdev4.12_ep81' can not be created
------------[ cut here ]------------
WARNING: at /home/l/latest/xxx/fs/sysfs/dir.c:425 sysfs_add_one+0x99/0xc0()
Modules linked in: usbhid hid nls_cp437 vfat fat usb_storage tun bitrev ipv6
arc4 ecb crypto_blkcipher cryptomgr crypto_algapi ath5k mac80211 sr_mod crc32
ohci1394 rtc_cmos cfg80211 ieee1394 floppy rtc_core ehci_hcd rtc_lib ff_memless
cdrom [last unloaded: hid]
Pid: 539, comm: bash Tainted: G W 2.6.25-rc8-mm1_64 #395
Call Trace:
[<ffffffff8022f07f>] warn_on_slowpath+0x5f/0x80
[<ffffffff80230197>] ? printk+0x67/0x70
[<ffffffff802d9bd0>] ? sysfs_ilookup_test+0x0/0x20
[<ffffffff802a12e8>] ? ifind+0x58/0xc0
[<ffffffff802d9bd0>] ? sysfs_ilookup_test+0x0/0x20
[<ffffffff802d9f49>] sysfs_add_one+0x99/0xc0
[<ffffffff802daf68>] sysfs_create_link+0xa8/0x130
[<ffffffff8038ebda>] device_add+0x2aa/0x4d0
[<ffffffff80310c26>] ? kobject_init+0x36/0x80
[<ffffffff8038ee19>] device_register+0x19/0x20
[<ffffffff803dbbec>] usb_create_ep_files+0x19c/0x320
[<ffffffff803dadb3>] usb_create_sysfs_intf_files+0xd3/0x100
[<ffffffff803d630c>] usb_set_configuration+0x3ac/0x5f0
[<ffffffff803df81a>] generic_probe+0x7a/0xb0
[<ffffffff803d83fa>] usb_probe_device+0x3a/0x40
[<ffffffff80390ceb>] driver_probe_device+0x9b/0x1a0
[<ffffffff803901b3>] driver_bind+0xb3/0x100
[<ffffffff8038f8a7>] drv_attr_store+0x27/0x30
[<ffffffff802d94ab>] sysfs_write_file+0xeb/0x140
[<ffffffff8028cc57>] vfs_write+0xc7/0x170
[<ffffffff8028d2f0>] sys_write+0x50/0x90
[<ffffffff8020b5eb>] system_call_after_swapgs+0x7b/0x80
---[ end trace 6ee6d593d4e510b4 ]---
I think, this is a 2.6.25-rc5-mm1 regression, there
while :; do
echo -n 4-1.2 >/sys/bus/usb/drivers/usb/unbind
echo -n 4-1.2 >/sys/bus/usb/drivers/usb/bind
usleep 10000
done
went just fine for about 2000 times. Also real disconnect/connect works just
fine (on disconnect the link disappears). Do you need kobject debug output?
The dir looks like:
...
usbdev4.10_ep83 ->
../../devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.3/4-1.3:1.0/usb_endpoint/usbdev4.10_ep83
usbdev4.12_ep81 ->
../../devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.2/4-1.2:1.0/usb_endpoint/usbdev4.12_ep81
^^^^
this is the unbound, the link is broken, there is no such device even after
binding it back.
usbdev4.1_ep00 ->
../../devices/pci0000:00/0000:00:1d.0/usb4/usb_endpoint/usbdev4.1_ep00
usbdev4.1_ep81 ->
../../devices/pci0000:00/0000:00:1d.0/usb4/4-0:1.0/usb_endpoint/usbdev4.1_ep81
usbdev4.5_ep00 ->
../../devices/pci0000:00/0000:00:1d.0/usb4/4-1/usb_endpoint/usbdev4.5_ep00
...
The device is:
Bus 004 Device 012: ID 045e:00f0 Microsoft Corp.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x045e Microsoft Corp.
idProduct 0x00f0
bcdDevice 1.01
iManufacturer 1 Microsoft Corporation
iProduct 2 Microsoft � Laser Mouse 6000
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 34
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Devices
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 2 Mouse
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 33 US
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 59
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0004 1x 4 bytes
bInterval 10
Device Status: 0x0000
(Bus Powered)
next prev parent reply other threads:[~2008-04-04 20:18 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-02 4:32 2.6.25-rc8-mm1 Andrew Morton
2008-04-02 5:40 ` 2.6.25-rc8-mm1 Dmitri Vorobiev
2008-04-02 6:03 ` 2.6.25-rc8-mm1 Andrew Morton
2008-04-02 17:33 ` 2.6.25-rc8-mm1 (mips build failure) Christoph Lameter
2008-04-02 18:29 ` Andrew Morton
2008-04-02 18:33 ` Christoph Lameter
2008-04-02 19:06 ` Sam Ravnborg
2008-04-03 16:02 ` Ralf Baechle
2008-04-03 22:17 ` Christoph Lameter
2008-04-03 23:26 ` Dmitri Vorobiev
2008-04-04 10:24 ` Ralf Baechle
2008-04-04 17:36 ` Christoph Lameter
2008-04-04 17:50 ` Christoph Lameter
2008-04-02 6:04 ` 2.6.25-rc8-mm1 Valdis.Kletnieks
2008-04-02 6:15 ` 2.6.25-rc8-mm1 Andrew Morton
2008-04-02 6:25 ` [BUG] 2.6.25-rc8-mm1 kernel panic while bootup on powerpc Kamalesh Babulal
2008-04-02 6:39 ` Andrew Morton
2008-04-02 7:08 ` Kamalesh Babulal
2008-04-02 7:17 ` Michael Ellerman
2008-04-02 17:09 ` Kamalesh Babulal
2008-04-02 18:15 ` Badari Pulavarty
2008-04-02 19:22 ` Badari Pulavarty
2008-04-02 21:57 ` Yinghai Lu
2008-04-02 22:24 ` Yinghai Lu
2008-04-04 9:24 ` Andy Whitcroft
2008-04-02 9:02 ` [BUILD_FAILURE] 2.6.25-rc8-mm1 build failure on x86_64 with randconfig Kamalesh Babulal
2008-04-02 10:49 ` 2.6.25-rc8-mm1 Miles Lane
2008-04-02 11:08 ` 2.6.25-rc8-mm1 Valdis.Kletnieks
2008-04-02 16:58 ` 2.6.25-rc8-mm1 Chatre, Reinette
2008-04-02 19:15 ` 2.6.25-rc8-mm1 Valdis.Kletnieks
2008-04-02 16:20 ` 2.6.25-rc8-mm1 sparc64 build problem: size of array 'type name' is negative Mariusz Kozlowski
2008-04-02 16:30 ` Andrew Morton
2008-04-02 19:12 ` 2.6.25-rc8-mm1 - BUG in fs/jbd/transaction.c Valdis.Kletnieks
2008-04-02 19:27 ` Josef Bacik
2008-04-02 19:39 ` Andrew Morton
2008-04-02 19:41 ` Josef Bacik
2008-04-03 18:18 ` Stephen Smalley
2008-04-03 23:02 ` James Morris
2008-04-04 12:46 ` Stephen Smalley
2008-04-06 23:54 ` James Morris
2008-04-04 10:15 ` Jan Kara
2008-04-04 12:53 ` 2.6.25-rc8-mm1 - BUG in fs/jbd/transaction.c' Josef Bacik
2008-04-03 18:25 ` 2.6.25-rc8-mm1 - BUG in fs/jbd/transaction.c Stephen Smalley
2008-04-02 19:30 ` Andrew Morton
2008-04-03 8:57 ` Jan Kara
2008-04-03 12:11 ` 2.6.25-rc8-mm1 Dave Airlie
2008-04-03 16:59 ` 2.6.25-rc8-mm1 Andrew Morton
2008-04-03 23:08 ` 2.6.25-rc8-mm1: Intel SATA boot failure Tilman Schmidt
2008-04-03 23:17 ` Andrew Morton
2008-04-09 14:29 ` Tilman Schmidt
2008-04-14 0:28 ` Tilman Schmidt
2008-04-14 2:05 ` Andrew Morton
2008-04-15 23:33 ` Tilman Schmidt
2008-04-04 20:16 ` Jiri Slaby [this message]
2008-04-04 20:51 ` usb unbind/bind => WARNING at fs/sysfs/dir.c [Was: 2.6.25-rc8-mm1] Greg KH
2008-04-04 21:23 ` Alan Stern
2008-04-05 3:46 ` Alan Stern
2008-04-05 4:37 ` Greg KH
2008-04-05 14:16 ` Alan Stern
2008-04-05 8:17 ` Jiri Slaby
2008-04-07 6:21 ` 2.6.25-rc8-mm1 - BUG: scheduling while atomic: swapper/0/0xffffffff Valdis.Kletnieks
2008-04-07 6:48 ` Andrew Morton
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=47F68CA0.7090007@gmail.com \
--to=jirislaby@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).