netdev - RE: usbnet transmit path 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: <AE90C24D6B3A694183C094C60CF0A2F6026B7327@saturn3.aculab.com>
Date:	Wed, 11 Sep 2013 14:00:33 +0100
From:	"David Laight" <David.Laight@...LAB.COM>
To:	"Oliver Neukum" <oliver@...kum.org>
Cc:	<netdev@...r.kernel.org>, "Ming Lei" <ming.lei@...onical.com>
Subject: RE: usbnet transmit path problems

> > 4) I read that USB3 has a different scheme for terminating bulk data
> >    that is a multiple of the packet size.
> >    Does this mean that the pad byte isn't needed for USB3?
> >    (Or are USB3 controllers/targets just as buggy?)
> 
> We don't have enough examples to tell.

Perhaps there should be a separate flag for USB3?
A device might have issues on USB2, but not USB3!

The flag is target specific - so I presume it isn't
a host/sending problem.

	David