linux-kernel - Re: tty: ctrl-c not always echoed, especially under load

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]

Message-ID: <20080811173911.07a3a9c5@lxorguk.ukuu.org.uk>
Date:	Mon, 11 Aug 2008 17:39:11 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Joe Peterson <joe@...rush.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: tty: ctrl-c not always echoed, especially under load

> I am working up an echo buffer (fifo) that would hold these characters until
> they can be sent (if the write is not possible), but since that means they
> will arrive at the tty later, their interleaving within the application output
> stream is not guaranteed, which again is a problem for the column logic.
> 
> I'm still looking into it - not trivial for sure...

First thought would be to simply fire all output through your buffer in
n_tty. It's not a performance critical bit of code and it would still be
fast as the usual case would be

	if (queue->length == 0)
		try_write_directly(...)
--
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/