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] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.1407211006190.875-100000@iolanthe.rowland.org>
Date:	Mon, 21 Jul 2014 10:06:37 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Amit Virdi <amit.virdi@...com>
cc:	linux-usb@...r.kernel.org, <linux-kernel@...r.kernel.org>,
	<gregkh@...uxfoundation.org>, <rdunlap@...radead.org>,
	<ming.lei@...onical.com>, <hdegoede@...hat.com>,
	<spear-devel@...t.st.com>
Subject: Re: [PATCH V2] usb: core: allow zero packet flag for interrupt urbs

On Mon, 21 Jul 2014, Amit Virdi wrote:

> Section 4.4.7.2 "Interrupt Transfer Bandwidth Requirements" of the USB3.0 spec
> says:
> 	A zero-length data payload is a valid transfer and may be useful for
> 	some implementations.
> 
> So, extend the logic of allowing URB_ZERO_PACKET to interrupt urbs too.
> Otherwise, the kernel throws warning of BOGUS transfer flags.
> 
> Signed-off-by: Amit Virdi <amit.virdi@...com>
> Acked-by: Hans de Goede <hdegoede@...hat.com>
> ---
>  drivers/usb/core/urb.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/usb/core/urb.c b/drivers/usb/core/urb.c
> index 991386ceb4ec..c9e8ee81b6b7 100644
> --- a/drivers/usb/core/urb.c
> +++ b/drivers/usb/core/urb.c
> @@ -454,6 +454,7 @@ int usb_submit_urb(struct urb *urb, gfp_t mem_flags)
>  			URB_FREE_BUFFER);
>  	switch (xfertype) {
>  	case USB_ENDPOINT_XFER_BULK:
> +	case USB_ENDPOINT_XFER_INT:
>  		if (is_out)
>  			allowed |= URB_ZERO_PACKET;
>  		/* FALLTHROUGH */

Acked-by: Alan Stern <stern@...land.harvard.edu>

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ