linux-kernel - Re: Keys get stuck

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:	Wed, 12 Mar 2008 10:47:01 -0400
From:	Theodore Tso <tytso@....edu>
To:	David Newall <davidn@...idnewall.com>
Cc:	Jiri Kosina <jkosina@...e.cz>, "Fred ." <eldmannen@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: Keys get stuck

On Wed, Mar 12, 2008 at 09:14:56PM +1030, David Newall wrote:
> It should be said that X implements auto-repeat out of necessity.  While
> the kernel can report key down and up events, its further interpretation
> of those events is not appropriate.  Many combinations of events are
> possible, such as keyboard plus mouse, and this precludes the kernel
> from providing a full interpretation.  It would be wrong for it to even
> try.  X is the proper place to implement auto-repeat for X.

The problem is that under heavy load the auto-repeat problem is real;
I've seen it as well, and it means that I've started to try to avoid
"make -j4" since that's a great way to trigger it.

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