linux-kernel - Re: What's in hid.git for 2.6.30

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: <alpine.LNX.2.00.0905011812330.22532@wotan.suse.de>
Date:	Fri, 1 May 2009 18:16:11 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Oliver Neukum <oliver@...kum.org>
Cc:	Guillaume Chazarain <guichaz@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: What's in hid.git for 2.6.30

On Fri, 1 May 2009, Oliver Neukum wrote:

> > If driven by usbhid, the only way how keyboard could be handled if not
> > claimed by hid-input is a userspace hiddev or hidraw driver. And we don't
> > suspend if hidraw/hiddev node is open, right?
> What happens if the node is closed? 

That's up to the userspace driver. If it is an input driver, it is 
probably using uinput to inject events into the input system, and 
therefore should properly unregister itself also from uinput together with 
closing the node.

> Will hid forget that a key had been pressed? I must admit that I can't 
> tell where in hid the key repetition logic is located.

The repetition is fully handled in the input core, not in the hid-input 
driver. So if the device is not handled by hid-input, we (the kernel 
driver) haven't registered with the input subsystem, and therefore no 
events go to input subsystem at all.

-- 
Jiri Kosina
SUSE Labs
--
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/