USB: dummy-hcd: accept mismatch between wLength and transfer length

This patch (as1269) fixes a bug in the way dummy_hcd handles control
URBs.  Currently it returns a -EOVERFLOW error if the wLength value in
the setup packet is different from the URB's transfer_buffer_length.

Other host controller drivers don't do this.  There's no reason the
two length values have to be equal, and in fact they sometimes aren't
-- a driver might set the transfer length to the maxpacket value in
order to handle buggy devices that don't respect wLength.

This patch simply removes the unnecessary check and error return.

Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>

diff --git a/drivers/usb/gadget/dummy_hcd.c b/drivers/usb/gadget/dummy_hcd.c
index a56b24d305f8209e869e8877091720b4b880e9b0..5e0966485188910b8716477c8422aebcdc03afef 100644 (file)
--- a/drivers/usb/gadget/dummy_hcd.c
+++ b/drivers/usb/gadget/dummy_hcd.c
@@ -1306,11 +1306,6 @@ restart:
                        setup = *(struct usb_ctrlrequest*) urb->setup_packet;
                        w_index = le16_to_cpu(setup.wIndex);
                        w_value = le16_to_cpu(setup.wValue);
-                       if (le16_to_cpu(setup.wLength) !=
-                                       urb->transfer_buffer_length) {
-                               status = -EOVERFLOW;
-                               goto return_urb;
-                       }
 
                        /* paranoia, in case of stale queued data */
                        list_for_each_entry (req, &ep->queue, queue) {