linux-kernel - Re: serial flow control appears broken

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] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 27 Jul 2007 11:11:42 -0700
From:	Lee Howard <faxguy@...ardsilvan.com>
To:	"Maciej W. Rozycki" <macro@...ux-mips.org>
CC:	Robert Hancock <hancockr@...w.ca>, linux-serial@...r.kernel.org,
	tytso@....edu, rmk@....linux.org.uk, linux-kernel@...r.kernel.org
Subject: Re: serial flow control appears broken

Maciej W. Rozycki wrote:

> The TTY line discipline driver could do that based on the amount of 
>received data present in its buffer.  And it should if asked to (a brief 
>look at drivers/char/n_tty.c reveals it does; obviously there may be a bug 
>somewhere though).  So could e.g. the SLIP and PPP line discipline 
>drivers, though the criteria might be different (apparently they do not, 
>which is a shame).
>
> The serial drivers have nothing to do about it -- all they can do is 
>pushing data upstream, to the discipline driver.  They can provide an 
>interface to hardware flow control features though, if implemented by a 
>given UART.
>

Thank you for this clarification.  So I should have more correctly been 
saying that "tty flow control appears broken".  Right?

I've asked the manufacturer to take a look at drivers/char/n_tty.c to 
see if they can't see anything obvious.

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/