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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Fri, 27 Jul 2007 11:00:37 -0700
From:	Lee Howard <faxguy@...ardsilvan.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
CC:	Uwe Kleine-König 
	<ukleinek@...ormatik.uni-freiburg.de>,
	linux-serial@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: serial flow control appears broken

Alan Cox wrote:

>As the flow control is driven by software on most 16x50 chips (there are
>a couple of exceptions) if we fail to empty the fifo fast enough then any
>flow control will be asserted too late to save the day.
>
>If you stop the application and do the following
>
>	cat /dev/ttywhatever
>	^Z
>	[stopped]
>
>(so you are asking the OS to buffer data but not ever reading it)
>
>and then fire data at it does the flow control eventually occur ?
>

Yes it does appear to.  I told the application to simply sleep(300) at 
the appropriate moment, and I watched the application and when it began 
the sleep I ran:

  cat /dev/ttyS1
  (lots of "garbage" began spewing forth)
  ^Z
  (about 2 or 3 seconds and the RTS light goes dark)

Thanks,

Lee.

-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ