Hi,
On Sat, Oct 15, 2016 at 12:28:21PM +, Dmitriy Samborskiy wrote:
> > From your description looks like the patch is reversed.
>
> Yes, it's reversed, sorry.
>
> > I'm not that familiar with usbredir code but looking at the code
> > if usbredirparser_do_write returns 0 the server should just
> From your description looks like the patch is reversed.
Yes, it's reversed, sorry.
> I'm not that familiar with usbredir code but looking at the code
> if usbredirparser_do_write returns 0 the server should just loop
> again.
You are right. I found this bug when I debugged the usbredir sources
>
> Hello,
>
> I'd like to propose a bugfix for usbredirparser.c usbredirparser_do_write()
> procedure, see below.
>
>
> Issue description:
>
> usbredirparser_do_write() does not handle EAGAIN properly.
> In case of large write parser->callb.write_func() returns 0 with
> errno=EAGAIN.
>
> The
Hello,
I'd like to propose a bugfix for usbredirparser.c usbredirparser_do_write()
procedure, see below.
Issue description:
usbredirparser_do_write() does not handle EAGAIN properly.
In case of large write parser->callb.write_func() returns 0 with errno=EAGAIN.
Then usbredirparser_do_write() c
