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: <20080313180333.GB4949@elf.ucw.cz>
Date:	Thu, 13 Mar 2008 19:03:33 +0100
From:	Pavel Machek <pavel@....cz>
To:	"Fred ." <eldmannen@...il.com>
Cc:	David Newall <davidn@...idnewall.com>,
	Jiri Kosina <jkosina@...e.cz>, linux-kernel@...r.kernel.org
Subject: Re: Keys get stuck

On Thu 2008-03-13 18:56:04, Fred . wrote:
> With so many people suffering from this bug (for a long time), and so
> many bright people here, why doesn't it get fixed?

With so many trolls out here it is hard to get any real work done.

> ...other operating systems don't suffer from this bug...

X is broken here... feel free to fix it. You could also test
2.6.25-rc4, perhaps it is fixed there? Disable GROUP_SCHED.

								Pavel

> On Thu, Mar 13, 2008 at 6:14 PM, Pavel Machek <pavel@....cz> wrote:
> >
> > On Wed 2008-03-12 21:14:56, David Newall wrote:
> >  > Jiri Kosina wrote:
> >  > > Very probably this is due to broken way how X themselves implement
> >  > > auto-repeat, instead of using kernel-provided auto-repeat functionality.
> >  >
> >  > 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.
> >
> >  No.
> >
> >  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.
> >
> >  --
> >  (english) http://www.livejournal.com/~pavelmachek
> >  (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
> >

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
pomozte zachranit klanovicky les:  http://www.ujezdskystrom.info/
--
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/