linux-kernel - Re: Visible Ctrl-C in latest kernels

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: <48B2BAE7.4010702@skyrush.com>
Date:	Mon, 25 Aug 2008 08:00:07 -0600
From:	Joe Peterson <joe@...rush.com>
To:	Willy Tarreau <w@....eu>
CC:	Chris Frey <cdfrey@...rsquare.net>,
	Vegard Nossum <vegard.nossum@...il.com>,
	linux-kernel@...r.kernel.org, Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: Visible Ctrl-C in latest kernels

Willy Tarreau wrote:
>>> Chris, yes, what you are now seeing on the newer kernel is correct.
>> Thanks guys.  I was not aware of this change before asking.  The change
>> makes sense.  I wasn't having any problems with it, just wondering where
>> it came from.
>>
>> Thanks for the enlightenment. :-)
> 
> I would not be surprized that it is what has caused delays for Ctrl-C
> to take effect for some of us. As discussed in another thread on the
> subject, the problem was relatively recent and not easy to reproduce.
> Now we have a patch to try to revert if/when we finally get a reproducible
> case.

It seems very unlikely that the echo has anything to do with it, other
than making the problem more visible.  See this post:

	http://marc.info/?l=linux-kernel&m=121526224222656&w=2

And to what patch of yours are you referring?

				-Joe

--
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/