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:	Thu, 13 Mar 2008 13:02:01 +0100
From:	Mike Galbraith <efault@....de>
To:	Jiri Kosina <jkosina@...e.cz>
Cc:	Jan Knutar <jk-lkml@....fi>, linux-kernel@...r.kernel.org,
	Hans-Peter Jansen <hpj@...la.net>,
	David Newall <davidn@...idnewall.com>,
	Theodore Tso <tytso@....edu>, "Fred ." <eldmannen@...il.com>
Subject: Re: Keys get stuck


On Thu, 2008-03-13 at 12:31 +0100, Jiri Kosina wrote:
> On Thu, 13 Mar 2008, Mike Galbraith wrote:
> 
> > > I'm not sure if it's the same issue or not, they don't repeat 
> > > "forever" for me, it just makes my speeellllliingggg llllooookkk 
> > > teerrriibbblle. Like that. Before this happens, letters usually stop 
> > > appearing on screen as I'm typing. I usually stop typing at that 
> > > point, since I know it will just become a mess.
> > Yes, that's the symptom I was refering to.  If you see that under
> > reasonable CPU load, and _without_ major swapping going on, then I'd be
> > suspicious of scheduler trouble.  Swap can definitely keep X off the cpu
> > for extended periods, and that seems to be what triggers the repeated
> > keys behavior.  (I've never troubleshot it, so must say _seems_)
> 
> I have a hard time calling this a kernel scheduler trouble. My 
> understanding is that X are sometimes unhappy how kernel schedules them 
> when under load, and that triggers bug in X autorepeat code.

Only if X is not getting CPU for long periods without swapping would I
become suspicious of the scheduler.  We recently had exactly this
trouble with the fair groups load balancing code (now reverted) and CPU
bound loads.  The bug is a symptom of latency woes, and the scheduler is
just one potential source worth watching.  In the heavy swapping case,
it's unlikely to be scheduler trouble, and yes, the bug lies elsewhere.

	-Mike

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