linux-kernel - Re: [BUG] 2.6.24-git usb reset problems

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: <479F34B4.9040001@panasas.com>
Date:	Tue, 29 Jan 2008 16:14:12 +0200
From:	Boaz Harrosh <bharrosh@...asas.com>
To:	Jens Axboe <jens.axboe@...cle.com>
CC:	Greg KH <greg@...ah.com>,
	Matthew Dharm <mdharm-usb@...-eyed-alien.net>,
	linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org,
	linux-scsi@...r.kernel.org
Subject: Re: [BUG] 2.6.24-git usb reset problems

On Tue, Jan 29 2008 at 16:11 +0200, Jens Axboe <jens.axboe@...cle.com> wrote:
> On Tue, Jan 29 2008, Boaz Harrosh wrote:
>> On Tue, Jan 29 2008 at 15:54 +0200, Jens Axboe <jens.axboe@...cle.com> wrote:
>>> On Tue, Jan 29 2008, Boaz Harrosh wrote:
>>>> Greg KH wrote:
>>>>> On Mon, Jan 28, 2008 at 09:49:35PM +0100, Jens Axboe wrote:
>>>>>> Hi,
>>>>>>
>>>>>> Running latest -git (head 91525300baf162e83e923b09ca286f9205e21522) and
>>>>>> connecting my cf usb storage device yields and endless stream of:
>>>>>>
>>>>>> Initializing USB Mass Storage driver...
>>>>>> scsi6 : SCSI emulation for USB Mass Storage devices
>>>>>> usb-storage: device found at 2
>>>>>> usb-storage: waiting for device to settle before scanning
>>>>>> usbcore: registered new interface driver usb-storage
>>>>>> USB Mass Storage support registered.
>>>>>> scsi 6:0:0:0: Direct-Access     Generic  STORAGE DEVICE   0125 PQ: 0
>>>>>> ANSI: 0
>>>>>> sd 6:0:0:0: [sdb] 4001760 512-byte hardware sectors (2049 MB)
>>>>>> sd 6:0:0:0: [sdb] Write Protect is off
>>>>>> sd 6:0:0:0: [sdb] Mode Sense: 02 00 00 00
>>>>>> sd 6:0:0:0: [sdb] Assuming drive cache: write through
>>>>>> sd 6:0:0:0: [sdb] 4001760 512-byte hardware sectors (2049 MB)
>>>>>> sd 6:0:0:0: [sdb] Write Protect is off
>>>>>> sd 6:0:0:0: [sdb] Mode Sense: 02 00 00 00
>>>>>> sd 6:0:0:0: [sdb] Assuming drive cache: write through
>>>>>>  sdb: sdb1
>>>>>> sd 6:0:0:0: [sdb] Attached SCSI removable disk
>>>>>> sd 6:0:0:0: Attached scsi generic sg1 type 0
>>>>>> scsi 6:0:0:1: Direct-Access     Generic  STORAGE DEVICE   0125 PQ: 0
>>>>>> ANSI: 0
>>>>>> usb 5-1: reset high speed USB device using ehci_hcd and address 2
>>>>>> usb 5-1: reset high speed USB device using ehci_hcd and address 2
>>>>>> usb 5-1: reset high speed USB device using ehci_hcd and address 2
>>>>>> usb 5-1: reset high speed USB device using ehci_hcd and address 2
>>>>>> usb 5-1: reset high speed USB device using ehci_hcd and address 2
>>>>>> usb 5-1: reset high speed USB device using ehci_hcd and address 2
>>>>>> usb 5-1: reset high speed USB device using ehci_hcd and address 2
>>>>>> [...]
>>>>>>
>>>>>> until I disconnect it. The device doesn't work. Worked fine in 2.6.24.
>>>>>> I'm attaching boot messages and my .config.
>>>>> That's a bit wierd, as we haven't added any USB patches to the -git tree
>>>>> yet after 2.6.24 :)
>>>>>
>>>>> Could this be caused by some scsi changes perhaps?
>>>>>
>>>>> thanks,
>>>>>
>>>>> greg k-h
>>>>> -
>>>> Yes it is ;)
>>>>
>>>> Jens could you test the patch below? if it works I'll submit a proper
>>>> patch. Please forgive me for the bug.
>>> No difference, still just a lot of resets.
>>>
>> Where you able to figure out which usb storage transport is used?
>>
>> in drivers/usb/storage/usb.c you have get_protocol() and get_transport()
>> functions. I'm not sure if these get stored in sysfs perhaps. This will
>> pinpoint better where to look. Let me research a bit. 
> 
> Did the quick'n easy and dumped it. Protocol is 'Transparent SCSI' and
> transport is 'Bulk'
> 
Sorry for the other noise. Thanks I'll have a look.
--
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/