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  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, 04 Jul 2008 15:17:26 -0600
From:	Joe Peterson <>
To:	Alan Cox <>
CC:	Elias Oltmanns <>,
	Török Edwin <>,
	Linux Kernel <>
Subject: Re: Ctrl+C doesn't interrupt process waiting for I/O

Alan Cox wrote:
>> disk activity process over each time it completed), it always broke out
>> after one ^C - one time took an extra second or two.  Note that I did
>> not run latencytop (did not have it compiled in my kernel) - if that is
>> required for the test, let me know, but I assume it is just for
>> gathering info when the issue occurs.
> I really don't think this is tty related looking at the code involved and
> also the lack of actual measurements presented. More likely scheduler and
> VM related changes.

Alan, many thanks for your assessment - it's greatly appreciated.  Now
that I've looked into it, the only peculiar thing I see is the redundant
flush_buffer call.  Do you think that should be removed anyway?  It
seems that the following two calls do the same thing in n_tty.c:


If this looks redundant, let me know, and I can submit a patch to just
call n_tty_flush_buffer(tty).

					-Thanks, Joe
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists