linux-kernel - Re: select() on /dev/input/eventX not level-triggered?

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: <20110523181312.GA20438@core.coreip.homeip.net>
Date:	Mon, 23 May 2011 11:13:12 -0700
From:	Dmitry Torokhov <dmitry.torokhov@...il.com>
To:	Pavel Machek <pavel@....cz>
Cc:	kernel list <linux-kernel@...r.kernel.org>,
	linux-input@...r.kernel.org
Subject: Re: select() on /dev/input/eventX not level-triggered?

On Fri, May 20, 2011 at 01:50:51AM +0200, Pavel Machek wrote:
> Hi!
> 
> I'm debugging strange behaviour on /dev/input/eventX ... it seems that
> select is not behaving level-triggered as it apparently should. I can
> reproduce it when hitting windows & alt keys.
> 
> Now, I really should rewrite it into C, first, but perhaps someone has
> an idea?

Is this with next or with mainline? In next we try not to signal that FD
is ready unless we have full packet in the buffer...

FWIW I see python indeed not reading the tail of events (btw the format
should be 'llhhi' and the size on 64 bit arches is 24, not 16) but when
I hacked evtest to use select and non-blockign read it all worked
properly.

Thanks.

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