| 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
| ||
|
Date: Sat, 05 May 2007 10:43:21 -0600 From: Paul Fulghum <paulkf@...rogate.com> To: Antonino Ingargiola <tritemio@...il.com> CC: Alan Cox <alan@...rguk.ukuu.org.uk>, linux-usb-users@...ts.sourceforge.net, linux-kernel@...r.kernel.org Subject: Re: [SOLVED] Serial buffer corruption [was Re: FTDI usb-serial possible bug] Antonino Ingargiola wrote: > The patch now boot properly and solves > completely the testcase with two serial lines: Good, thanks for testing. > I think this patch should be included in mainline, since if one flushes > the input buffer, really want to flush the entire buffer chain and > doesn't want to read any old data _after_ a flush. I will submit the patch, it's clearly needed. > However I also tested a usb-serial device (that uses the cdc-acm > driver) and in this case I still need _two_ flushInput() to totally > flush the input buffer. > > There can be another *secondary buffer* in the usb-serial driver? Can > this buffer be emptied out too? Very possible, but I'm not familiar with that. There is not an input flush method for the tty driver and individual drivers don't process that ioctl. The tty drivers I've seen immediately pass receive data to the tty buffering and I'm not sure why a driver would behave otherwise. -- Paul - 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