<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/linux.git/drivers/usb/storage, branch v2.6.32</title>
<subtitle>Linux kernel stable tree (mirror)</subtitle>
<id>https://git.radix-linux.su/kernel/linux.git/atom?h=v2.6.32</id>
<link rel='self' href='https://git.radix-linux.su/kernel/linux.git/atom?h=v2.6.32'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/'/>
<updated>2009-10-14T21:54:44+00:00</updated>
<entry>
<title>usb-storage: Workaround devices with bogus sense size</title>
<updated>2009-10-14T21:54:44+00:00</updated>
<author>
<name>Benjamin Herrenschmidt</name>
<email>benh@kernel.crashing.org</email>
</author>
<published>2009-10-13T04:53:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=b8430e1b82b7e514d76a88eb70a7d8831d50df1e'/>
<id>urn:sha1:b8430e1b82b7e514d76a88eb70a7d8831d50df1e</id>
<content type='text'>
usb-storage: Workaround devices with bogus sense size

Some devices, such as Huawei E169, advertise more than the standard
amount of sense data, causing us to set US_FL_SANE_SENSE, assuming
they support it. However, they subsequently fail the request sense
with that size.

This works around it generically. When a sense request fails due to
a device returning an error, US_FL_SANE_SENSE was set, and that sense
request used a larger sense size, we retry with a smaller size before
giving up.

Based on an original patch by Ben Efros &lt;ben@pc-doctor.com&gt;

Signed-off-by: Benjamin Herrenschmidt &lt;benh@kernel.crashing.org&gt;
Acked-by: Alan Stern &lt;stern@rowland.harvard.edu&gt;
Cc: stable &lt;stable@kernel.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;


</content>
</entry>
<entry>
<title>USB: storage: When a device returns no sense data, call it a Hardware Error</title>
<updated>2009-10-09T20:52:08+00:00</updated>
<author>
<name>Alan Stern</name>
<email>stern@rowland.harvard.edu</email>
</author>
<published>2009-10-06T18:07:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=f1a0743bc0e7a30c032b1eb78f6a2b0f805b4597'/>
<id>urn:sha1:f1a0743bc0e7a30c032b1eb78f6a2b0f805b4597</id>
<content type='text'>
This patch (as1294) fixes a problem that has plagued users for several
kernel releases.  Some USB mass-storage devices don't return any sense
data when they encounter certain kinds of errors.  The SCSI layer
interprets this to mean that the operation should be retried, and the
same thing happens -- over and over again with no limit.  In some
circumstances (such as when a bus reset occurs) that is the right
thing to do, but not here.

The patch checks for this condition (a transport failure with no sense
data) and changes the result code to DID_ERROR and the sense code to
Hardware Error.  This does get only a limited number of retries, and
so the command will fail relatively quickly instead of getting stuck
in an infinite loop.

This fixes a large part of Bugzilla #14118.

Signed-off-by: Alan Stern &lt;stern@rowland.harvard.edu&gt;
Tested-by: Mantas Mikulenas &lt;grawity@gmail.com&gt;
CC: stable &lt;stable@kernel.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>USB: storage: iRiver P7 UNUSUAL_DEV patch</title>
<updated>2009-10-09T20:52:07+00:00</updated>
<author>
<name>Sergey Pinaev</name>
<email>dfo@antex.ru</email>
</author>
<published>2009-09-17T13:26:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=2f13612a86dd785d581e29aed4db2fb98ba507ca'/>
<id>urn:sha1:2f13612a86dd785d581e29aed4db2fb98ba507ca</id>
<content type='text'>
Signed-off-by: Phil Dibowitz &lt;phil@ipom.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>USB: unusual_devs.h: drop some unneeded floppy entries</title>
<updated>2009-09-23T13:46:38+00:00</updated>
<author>
<name>Pete Zaitcev</name>
<email>zaitcev@redhat.com</email>
</author>
<published>2009-08-21T02:00:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=fd4f3a931f6e047e88bc8c6023666acad957109a'/>
<id>urn:sha1:fd4f3a931f6e047e88bc8c6023666acad957109a</id>
<content type='text'>
We set pdt_1f_for_no_lun for UFI devices, so most floppy entiries should
be unnecessary. This patch removes three entries which I'm certain are.
 - For Mitsumi I have a customer with RHEL 5 (bz#514296)
 - For SMSC I accessed Novell's Bugzilla and verified the entry
 - For Y-E I tested the patch with the actual device

Signed-off-by: Pete Zaitcev &lt;zaitcev@redhat.com&gt;
Signed-off-by: Phil Dibowitz &lt;phil@ipom.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>USB: usb-storage fails to attach to Huawei Datacard cdrom device</title>
<updated>2009-09-23T13:46:32+00:00</updated>
<author>
<name>fangxiaozhi</name>
<email>huananhu@huawei.com</email>
</author>
<published>2009-08-07T04:30:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=d0defb855c8504c49b92bdc0203689ce9b4cf7ba'/>
<id>urn:sha1:d0defb855c8504c49b92bdc0203689ce9b4cf7ba</id>
<content type='text'>
In this patch, we always make the return value of function
usb_stor_huawei_e220_init to be zero. Then it will not prevent usb-storage
driver from attaching to the CDROM device of Huawei Datacard.

Signed-off-by: fangxiaozhi &lt;huananhu@huawei.com&gt;
Cc: stable &lt;stable@kernel.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>USB: storage: Drop an unneeded a NULL test</title>
<updated>2009-09-23T13:46:29+00:00</updated>
<author>
<name>Julia Lawall</name>
<email>julia@diku.dk</email>
</author>
<published>2009-07-19T15:29:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=64aebe73152ab3a9f5f426baaf65db632bd72c13'/>
<id>urn:sha1:64aebe73152ab3a9f5f426baaf65db632bd72c13</id>
<content type='text'>
In each case, the NULL test is not necessary because the function is static
and at the only places where it is called, the us argument has already been
dereferenced.

The semantic patch that finds the problem is as follows:
(http://www.emn.fr/x-info/coccinelle/)

// &lt;smpl&gt;
@@
type T;
expression E,E1;
identifier i,fld;
statement S;
@@

- T i = E-&gt;fld;
+ T i;
  ... when != E=E1
      when != i
  if (E == NULL||...) S
+ i = E-&gt;fld;
// &lt;/smpl&gt;

Signed-off-by: Julia Lawall &lt;julia@diku.dk&gt;
Cc: Matthew Dharm &lt;mdharm-usb@one-eyed-alien.net&gt;
Cc: Alan Stern &lt;stern@rowland.harvard.edu&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>USB: storage: fix a resume path GFP_NOIO must be used</title>
<updated>2009-09-23T13:46:15+00:00</updated>
<author>
<name>Oliver Neukum</name>
<email>oliver@neukum.org</email>
</author>
<published>2009-08-26T17:56:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=e5dc8ae121592239c2a2521d383bcb789849b2a3'/>
<id>urn:sha1:e5dc8ae121592239c2a2521d383bcb789849b2a3</id>
<content type='text'>
In the resume path of a block driver GFP_NOIO must be used to
avoid a possible deadlock. The onetouch subdriver of storage violates
the requirement.

Signed-off-by: Oliver Neukum &lt;oliver@neukum.org&gt;
Cc: stable &lt;stable@kernel.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>USB: storage: include Prolific Technology USB drive in unusual_devs list</title>
<updated>2009-08-07T23:05:14+00:00</updated>
<author>
<name>Rogerio Brito</name>
<email>rbrito@ime.usp.br</email>
</author>
<published>2009-08-06T22:20:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=c15e3ca1d822abba78c00b1ffc3e7b382a50396e'/>
<id>urn:sha1:c15e3ca1d822abba78c00b1ffc3e7b382a50396e</id>
<content type='text'>
Add a quirk entry for the Leading Driver UD-11 usb flash drive.

As Alan Stern told me, the device doesn't deal correctly with the
locking media feature of the device, and this patch incorporates it.

Compiled, tested, working.

Signed-off-by: Rogerio Brito &lt;rbrito@ime.usp.br&gt;
Cc: Phil Dibowitz &lt;phil@ipom.com&gt;
Cc: Alan Stern &lt;stern@rowland.harvard.edu&gt;
Cc: Robert Hancock &lt;hancockrwd@gmail.com&gt;
Cc: stable &lt;stable@kernel.org&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>USB: storage: raise timeout in usb_stor_Bulk_max_lun</title>
<updated>2009-07-28T21:31:09+00:00</updated>
<author>
<name>Giacomo Lozito</name>
<email>james@develia.org</email>
</author>
<published>2009-07-13T21:23:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=7a777919bbeec3eac1d7904a728a60e9c2bb9c67'/>
<id>urn:sha1:7a777919bbeec3eac1d7904a728a60e9c2bb9c67</id>
<content type='text'>
Requests to get max LUN, for certain USB storage devices, require a
longer timeout before a correct reply is returned. This happens for a
Realtek USB Card Reader (0bda:0152), which has a max LUN of 3 but is set
to 0, thus losing functionality, because of the timeout occurring too
quickly.

Raising the timeout value fixes the issue and might help other devices
to return a correct max LUN value as well.

Signed-off-by: Giacomo Lozito &lt;james@develia.org&gt;
Acked-by: Alan Stern &lt;stern@rowland.harvard.edu&gt;
Cc: stable &lt;stable@kernel.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>USB: Fix option_ms regression in 2.6.31-rc2</title>
<updated>2009-07-12T22:16:40+00:00</updated>
<author>
<name>Jonathan McDowell</name>
<email>noodles@earth.li</email>
</author>
<published>2009-07-05T11:29:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=2ab2178c3303583a0551f6b6bf4ba070afbf875f'/>
<id>urn:sha1:2ab2178c3303583a0551f6b6bf4ba070afbf875f</id>
<content type='text'>
Commit 32ebbe7b6ad44ae9c276419710b56de6ba705303 which filters the
SCSI REZERO command in option_ms based on a SCSI INQUIRY with a vendor
of Option breaks my Option Icon 225 (0af0:6971). This device returns a
vendor of ZCOPTION for the ZeroCD device. The following trivial patch
fixes things for me.

Signed-Off-By: Jonathan McDowell &lt;noodles@earth.li&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
</feed>
