| 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: Fri, 29 Jul 2011 14:06:50 -0400 From: lsorense@...lub.uwaterloo.ca (Lennart Sorensen) To: Lennart Sorensen <lsorense@...lub.uwaterloo.ca> Cc: Alan Cox <alan@...rguk.ukuu.org.uk>, linux-serial@...r.kernel.org, linux-kernel@...r.kernel.org, Breno Leitao <leitao@...ux.vnet.ibm.com> Subject: Re: Very strange data loss with jsm driver On Fri, Jul 29, 2011 at 12:53:42PM -0400, Lennart Sorensen wrote: > On Fri, Jul 29, 2011 at 05:27:36PM +0100, Alan Cox wrote: > > > The trigger point appears to be lines of up to 14 bytes, followed by > > > a newline. With 15 bytes or more per line it seems to be OK. > > > > > > Anyone got a clue? > > > > FIFO size perhaps - and some kind of missed wakeup or tx handling bug ? > > FIFO size is 64bytes, so that doesn't immediately sound related. > > The thing I find weird is that it thinks everything was sent right away. > > Also why should the newline have anything to do with it? If you send > 100100 bytes should it matter where the newlines are unless the tty > layer or the driver is interpreting the newlines for some reason. Same breakage on 2.6.18. I suspect this has always been broken. Hmm. I noticed fifosize in the uart_port info is set to 16, even though the fifo size is actually 64 bytes as all actual driver bits know. What is fifosize actually used for? -- Len Sorensen -- 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