linux-kernel - Re: [BUG] usb-storage: Error in queuecommand: us->srb = ffff88006a338480

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: <Pine.LNX.4.44L0.0811061435070.23473-100000@iolanthe.rowland.org>
Date:	Thu, 6 Nov 2008 14:36:40 -0500 (EST)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Andrew Morton <akpm@...ux-foundation.org>
cc:	Brian Kysela <bkysela@...il.com>, <linux-kernel@...r.kernel.org>,
	Jens Axboe <jens.axboe@...cle.com>,
	<linux-usb@...r.kernel.org>, <linux-scsi@...r.kernel.org>
Subject: Re: [BUG] usb-storage: Error in queuecommand: us->srb = ffff88006a338480

On Thu, 6 Nov 2008, Andrew Morton wrote:

> > The error message:
> > 
> > > [  152.701070] usb-storage: Error in queuecommand: us->srb = ffff88007dfd0680
> > 
> > means that the SCSI layer has told usb-storage to start a new command 
> > before the old one completed.  This could happen, for example, if the 
> > SCSI layer had gotten confused and tried to cancel a command that 
> > wasn't running -- then it would think usb-storage was idle when in fact 
> > it was still busy.  (This was the failure mechanism resulting from the 
> > timeout changes.)
> > 
> 
> OK, thanks.  I'll cc linux-scsi, but I have this-wont-be-getting-fixed
> feelings on this one :(
> 
> I wonder what's special about Brian's setup.

Brian, if you can use usbmon to monitor what happens during the file 
copy and subsequent error, it might provide a clue.  Instructions are 
in the kernel source file Documentation/usb/usbmon.txt.

Alan Stern

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