linux-kernel - Re: [PATCH] Revert "USB: serial: ch341: fix character loss at high transfer rates"

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <YSTzPIkwNDOON5j8@hovoldconsulting.com>
Date:   Tue, 24 Aug 2021 15:25:16 +0200
From:   Johan Hovold <johan@...nel.org>
To:     Willy Tarreau <w@....eu>
Cc:     linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
        Paul Größel <pb.g@....de>,
        stable@...r.kernel.org
Subject: Re: [PATCH] Revert "USB: serial: ch341: fix character loss at high
 transfer rates"

On Tue, Aug 24, 2021 at 02:32:32PM +0200, Willy Tarreau wrote:
> On Tue, Aug 24, 2021 at 02:19:26PM +0200, Johan Hovold wrote:
> > This reverts commit 3c18e9baee0ef97510dcda78c82285f52626764b.
> > 
> > These devices do not appear to send a zero-length packet when the
> > transfer size is a multiple of the bulk-endpoint max-packet size. This
> > means that incoming data may not be processed by the driver until a
> > short packet is received or the receive buffer is full.
> > 
> > Revert back to using endpoint-sized receive buffers to avoid stalled
> > reads.
> 
> Sorry for this, I didn't notice any issue here (aside for the chip
> working where it used not to). I have no idea what these zero-length
> packets correspond to, nor why they're affected by the transfer size.
> Do you have any idea what I should look for ? Because without that
> patch, the device is unusable for me :-/

Zero-length packets are used to indicate completion of bulk transfers
that are multiples of the endpoint max-packet size (as per the USB
spec). Without those the host controller driver doesn't now that the
transfer is complete and that it should call the driver completion
callback (and instead waits for the other completion conditions).

It may be possible to configure the device to send ZLPs somehow but
since there's no public documentation for the protocol that may require
some reverse engineering.

Johan