public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Peterson <joe@skyrush.com>
To: Willy Tarreau <w@1wt.eu>
Cc: Chris Frey <cdfrey@foursquare.net>,
	Vegard Nossum <vegard.nossum@gmail.com>,
	linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: Visible Ctrl-C in latest kernels
Date: Mon, 25 Aug 2008 08:00:07 -0600	[thread overview]
Message-ID: <48B2BAE7.4010702@skyrush.com> (raw)
In-Reply-To: <20080825122024.GA19337@1wt.eu>

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


  reply	other threads:[~2008-08-25 14:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-22 20:15 Visible Ctrl-C in latest kernels Chris Frey
2008-08-23  9:53 ` Vegard Nossum
2008-08-23 17:52   ` Joe Peterson
2008-08-24  1:02     ` Chris Frey
2008-08-25 12:20       ` Willy Tarreau
2008-08-25 14:00         ` Joe Peterson [this message]
2008-08-25 14:13           ` Willy Tarreau
2008-08-25 14:29             ` Joe Peterson
2008-08-25 17:37         ` David Newall
2008-08-25 18:03           ` Joe Peterson
2008-08-26  1:08             ` Joe Peterson
2008-08-26  7:40               ` David Newall

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48B2BAE7.4010702@skyrush.com \
    --to=joe@skyrush.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=cdfrey@foursquare.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vegard.nossum@gmail.com \
    --cc=w@1wt.eu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox