linux-kernel - Re: [PATCH 2/2] uinput: Use input_inject_event in uinput_inject

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:	Wed, 11 Sep 2013 10:26:10 +1000
From:	Ryan Mallon <rmallon@...il.com>
To:	Dmitry Torokhov <dmitry.torokhov@...il.com>
CC:	rydberg@...omail.se, carl@...labs.com, linux-input@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] uinput: Use input_inject_event in uinput_inject_event

On 11/09/13 10:12, Dmitry Torokhov wrote:
> Hi Ryan,
> 
> On Wed, Sep 11, 2013 at 09:32:53AM +1000, Ryan Mallon wrote:
>> Call input_inject_event rather than input_event in uinput_inject_event. This
>> mirrors the behaviour of evdev_write. input_inject_event will ignore the
>> injected event if the uinput input device has been grabbed for exclusive
>> access by a handler other than uinput.
> 
> uinput is not an input handler but input driver and therefore should
> continue using input_event().

Ah, I wasn't sure about this, which is why I broke it out into a
separate patch. Sorry for the noise.

~Ryan


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