On Wed, Jul 22, 2015 at 11:55:32AM -0500, Jeremy White wrote:
> I privately wrote to the Intel authors of that patch a week ago; I've
> publicly included them in this thread as well. As far as I can tell,
> they've been silent on this front since November; I fear that they may
> have moved on, or
On Wed, Nov 12, 2014 at 05:03:18PM -0500, Alan Stern wrote:
> On Wed, 12 Nov 2014, Sean O. Stalley wrote:
> > Our plan to support multiple MA devices is to have them all connected
> > to the same virtual host controller, so only 1 would be needed.
> >
> > Woul
Sorry, for got to respond to a couple comments. See responses below.
On Wed, Nov 12, 2014 at 01:40:21PM -0800, Sean O. Stalley wrote:
> Thanks for reviewing. My responses are inline.
>
> Greg has asked that we clean up this code internally before we
> send out another patchset to
Thanks for reviewing. My responses are inline.
Greg has asked that we clean up this code internally before we
send out another patchset to the mailing list. I will address
the issues you pointed out, but it may be a while before you see
another patchset.
Thanks Again,
Sean
On Tue, Nov 11, 2014 a
.
Thanks,
Sean O. Stalley
On Wed, Nov 12, 2014 at 09:35:42AM +0100, Oliver Neukum wrote:
> On Mon, 2014-11-10 at 18:09 -0800, Stephanie Wallick wrote:
> > diff --git a/drivers/staging/mausb/drivers/mausb_hub.c
> > b/drivers/staging/mausb/drivers/mausb_hub.c
> > new file mode 100
s.
We won't resubmit the driver until a senior kernel developer has signed off on
it.
Sincerely,
Sean O. Stalley
Stephanie S. Wallick
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
From: "Sean O. Stalley"
Change the default wMaxPacketSize value for EP0 of Full Speed
devices from the maximum possible size (64) to the minimum (8).
All full speed devices support a packet size of 8, but not all
support a size of 64.
No packet longer than 8 bytes is ever read from
Descriptor for hubs, defined
in the USB3.0 Spec, section 10.13.1 ) the write would overflow
the buffer and corrupt the stack. This patch addresses this
behavior.
Acked-by: Alan Stern
Signed-off-by: Sean O. Stalley
---
drivers/usb/core/hcd.c | 24 +---
1 file changed, 17
Descriptor for hubs, defined
in the USB3.0 Spec, section 10.13.1 ) the write would overflow
the buffer and corrupt the stack. This patch addresses this
behavior.
Acked-by: Alan Stern
Signed-off-by: Sean O. Stalley
---
drivers/usb/core/hcd.c | 24 +---
1 file changed, 17
Descriptor for hubs, defined
in the USB3.0 Spec, section 10.13.1 ) the write would overflow
the buffer and corrupt the stack. This patch addresses this
behavior.
Signed-off-by: Sean O. Stalley
---
drivers/usb/core/hcd.c | 24 +---
1 file changed, 17 insertions(+), 7 deletions
Descriptor for hubs, defined
in the USB3.0 Spec, section 10.13.1 ) the write would overflow
the buffer and corrupt the stack. This patch addresses this
behavior.
Signed-off-by: Sean O. Stalley
---
drivers/usb/core/hcd.c | 24 +---
1 file changed, 17 insertions(+), 7 deletions
Descriptor for hubs, defined
in the USB3.0 Spec, section 10.13.1 ) the write would overflow
the buffer and corrupt the stack. This patch addresses this
behavior.
Signed-off-by: Sean O. Stalley
---
drivers/usb/core/hcd.c | 23 ---
1 file changed, 16 insertions(+), 7 deletions
as being as large as the URB buffer ( via
wLength ).
when the hcd attempts to write a descriptor containing more than
15 bytes ( such as the Standard BOS Descriptor for hubs, defined
in the USB3.0 Spec, section 10.13.1 ) causes tbuf to overflow
onto the stack.
Signed-off-by: Sean O. Stalley
descriptors. Option 2
circumvents tbuf and passes nongeneric descriptors (such as BOS
descriptors) directly to the buffer in the urb, preventing the
overflow.
A third option would be to rewrite the rh_call function.
Sean O. Stalley (1):
rh_call_control tbuf overflow fix
Option 1:
drivers
as being as large as the URB buffer ( via
wLength ).
when the hcd attempts to write a descriptor containing more than
15 bytes ( such as the Standard BOS Descriptor for hubs, defined
in the USB3.0 Spec, section 10.13.1 ) causes tbuf to overflow
onto the stack.
Signed-off-by: Sean O. Stalley
15 matches
Mail list logo
