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]

Message-ID: <20080314133019.GE1289@csclub.uwaterloo.ca>
Date:	Fri, 14 Mar 2008 09:30:19 -0400
From:	lsorense@...lub.uwaterloo.ca (Lennart Sorensen)
To:	Pavel Machek <pavel@....cz>
Cc:	David Newall <davidn@...idnewall.com>,
	Jiri Kosina <jkosina@...e.cz>, "Fred ." <eldmannen@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: Keys get stuck

On Thu, Mar 13, 2008 at 06:14:26PM +0100, Pavel Machek wrote:
> hw is proper place to implement autorepeat, and along with some
> buffering, it has chance to work. Kernel is not real-time, and X are
> definitely not real-time, while autorepeat is real-time operation.
> 
> It actually mostly works in ps/2 case. Buffer in hardware means that
> pretty big interrupt delays can be tolerated without problems.

So does the keyboard events generate something like this then:

KEY_x_DOWN
KEY_x_REPEAT
KEY_x_UP

If so then X certainly could get all the keyboard information I imagine
it needs from the kernel, but otherwise I am not sure how it could.  A
repeated series of key down events are not enough since some keys you
don't want repeated you just want to know when the key is held down and
when it isn't.

I just hope someone figures it out since I would love to stop getting
duplicate characters whenever the system is under a bit of load in X.

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