* [PATCH 1/2] uinput: Support injecting multiple events in one write() call
@ 2013-09-10 23:32 Ryan Mallon
2013-09-10 23:32 ` [PATCH 2/2] uinput: Use input_inject_event in uinput_inject_event Ryan Mallon
2013-09-11 0:14 ` [PATCH 1/2] uinput: Support injecting multiple events in one write() call Dmitry Torokhov
0 siblings, 2 replies; 6+ messages in thread
From: Ryan Mallon @ 2013-09-10 23:32 UTC (permalink / raw)
To: dmitry.torokhov, rydberg; +Cc: carl, linux-input, linux-kernel, Ryan Mallon
Rework the code in uinput_inject_event so that it matches the code in
evdev_write and allows injecting more than one event, or zero events.
Signed-off-by: Ryan Mallon <rmallon@gmail.com>
---
drivers/input/misc/uinput.c | 14 +++++++++-----
1 file changed, 9 insertions(+), 5 deletions(-)
diff --git a/drivers/input/misc/uinput.c b/drivers/input/misc/uinput.c
index a0a4bba..6aea346 100644
--- a/drivers/input/misc/uinput.c
+++ b/drivers/input/misc/uinput.c
@@ -434,16 +434,20 @@ static ssize_t uinput_inject_event(struct uinput_device *udev,
const char __user *buffer, size_t count)
{
struct input_event ev;
+ size_t bytes = 0;
- if (count < input_event_size())
+ if (count != 0 && count < input_event_size())
return -EINVAL;
- if (input_event_from_user(buffer, &ev))
- return -EFAULT;
+ while (bytes + input_event_size() <= count) {
+ if (input_event_from_user(buffer + bytes, &ev))
+ return -EFAULT;
- input_event(udev->dev, ev.type, ev.code, ev.value);
+ input_event(udev->dev, ev.type, ev.code, ev.value);
+ bytes += input_event_size();
+ }
- return input_event_size();
+ return bytes;
}
static ssize_t uinput_write(struct file *file, const char __user *buffer,
--
1.7.9.7
^ permalink raw reply related [flat|nested] 6+ messages in thread* [PATCH 2/2] uinput: Use input_inject_event in uinput_inject_event
2013-09-10 23:32 [PATCH 1/2] uinput: Support injecting multiple events in one write() call Ryan Mallon
@ 2013-09-10 23:32 ` Ryan Mallon
2013-09-11 0:12 ` Dmitry Torokhov
2013-09-11 0:14 ` [PATCH 1/2] uinput: Support injecting multiple events in one write() call Dmitry Torokhov
1 sibling, 1 reply; 6+ messages in thread
From: Ryan Mallon @ 2013-09-10 23:32 UTC (permalink / raw)
To: dmitry.torokhov, rydberg; +Cc: carl, linux-input, linux-kernel, Ryan Mallon
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.
Signed-off-by: Ryan Mallon <rmallon@gmail.com>
---
drivers/input/misc/uinput.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/input/misc/uinput.c b/drivers/input/misc/uinput.c
index 6aea346..0962ecb 100644
--- a/drivers/input/misc/uinput.c
+++ b/drivers/input/misc/uinput.c
@@ -443,7 +443,7 @@ static ssize_t uinput_inject_event(struct uinput_device *udev,
if (input_event_from_user(buffer + bytes, &ev))
return -EFAULT;
- input_event(udev->dev, ev.type, ev.code, ev.value);
+ input_inject_event(udev->dev, ev.type, ev.code, ev.value);
bytes += input_event_size();
}
--
1.7.9.7
^ permalink raw reply related [flat|nested] 6+ messages in thread
* Re: [PATCH 2/2] uinput: Use input_inject_event in uinput_inject_event
2013-09-10 23:32 ` [PATCH 2/2] uinput: Use input_inject_event in uinput_inject_event Ryan Mallon
@ 2013-09-11 0:12 ` Dmitry Torokhov
2013-09-11 0:26 ` Ryan Mallon
0 siblings, 1 reply; 6+ messages in thread
From: Dmitry Torokhov @ 2013-09-11 0:12 UTC (permalink / raw)
To: Ryan Mallon; +Cc: rydberg, carl, linux-input, linux-kernel
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().
Thanks.
--
Dmitry
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH 2/2] uinput: Use input_inject_event in uinput_inject_event
2013-09-11 0:12 ` Dmitry Torokhov
@ 2013-09-11 0:26 ` Ryan Mallon
0 siblings, 0 replies; 6+ messages in thread
From: Ryan Mallon @ 2013-09-11 0:26 UTC (permalink / raw)
To: Dmitry Torokhov; +Cc: rydberg, carl, linux-input, linux-kernel
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH 1/2] uinput: Support injecting multiple events in one write() call
2013-09-10 23:32 [PATCH 1/2] uinput: Support injecting multiple events in one write() call Ryan Mallon
2013-09-10 23:32 ` [PATCH 2/2] uinput: Use input_inject_event in uinput_inject_event Ryan Mallon
@ 2013-09-11 0:14 ` Dmitry Torokhov
2013-09-11 0:29 ` Ryan Mallon
1 sibling, 1 reply; 6+ messages in thread
From: Dmitry Torokhov @ 2013-09-11 0:14 UTC (permalink / raw)
To: Ryan Mallon; +Cc: rydberg, carl, linux-input, linux-kernel
Hi Ryan,
On Wed, Sep 11, 2013 at 09:32:52AM +1000, Ryan Mallon wrote:
> Rework the code in uinput_inject_event so that it matches the code in
> evdev_write and allows injecting more than one event, or zero events.
>
> Signed-off-by: Ryan Mallon <rmallon@gmail.com>
> ---
> drivers/input/misc/uinput.c | 14 +++++++++-----
> 1 file changed, 9 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/input/misc/uinput.c b/drivers/input/misc/uinput.c
> index a0a4bba..6aea346 100644
> --- a/drivers/input/misc/uinput.c
> +++ b/drivers/input/misc/uinput.c
> @@ -434,16 +434,20 @@ static ssize_t uinput_inject_event(struct uinput_device *udev,
> const char __user *buffer, size_t count)
> {
> struct input_event ev;
> + size_t bytes = 0;
>
> - if (count < input_event_size())
> + if (count != 0 && count < input_event_size())
> return -EINVAL;
>
> - if (input_event_from_user(buffer, &ev))
> - return -EFAULT;
> + while (bytes + input_event_size() <= count) {
> + if (input_event_from_user(buffer + bytes, &ev))
> + return -EFAULT;
Unless the failure is in the very first packet we should tell the user
how many bytes we have transferred successfully instead of returning
-EFAULT.
Thanks.
--
Dmitry
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [PATCH 1/2] uinput: Support injecting multiple events in one write() call
2013-09-11 0:14 ` [PATCH 1/2] uinput: Support injecting multiple events in one write() call Dmitry Torokhov
@ 2013-09-11 0:29 ` Ryan Mallon
0 siblings, 0 replies; 6+ messages in thread
From: Ryan Mallon @ 2013-09-11 0:29 UTC (permalink / raw)
To: Dmitry Torokhov; +Cc: rydberg, carl, linux-input, linux-kernel
On 11/09/13 10:14, Dmitry Torokhov wrote:
> Hi Ryan,
>
> On Wed, Sep 11, 2013 at 09:32:52AM +1000, Ryan Mallon wrote:
>> Rework the code in uinput_inject_event so that it matches the code in
>> evdev_write and allows injecting more than one event, or zero events.
>>
>> Signed-off-by: Ryan Mallon <rmallon@gmail.com>
>> ---
>> drivers/input/misc/uinput.c | 14 +++++++++-----
>> 1 file changed, 9 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/input/misc/uinput.c b/drivers/input/misc/uinput.c
>> index a0a4bba..6aea346 100644
>> --- a/drivers/input/misc/uinput.c
>> +++ b/drivers/input/misc/uinput.c
>> @@ -434,16 +434,20 @@ static ssize_t uinput_inject_event(struct uinput_device *udev,
>> const char __user *buffer, size_t count)
>> {
>> struct input_event ev;
>> + size_t bytes = 0;
>>
>> - if (count < input_event_size())
>> + if (count != 0 && count < input_event_size())
>> return -EINVAL;
>>
>> - if (input_event_from_user(buffer, &ev))
>> - return -EFAULT;
>> + while (bytes + input_event_size() <= count) {
>> + if (input_event_from_user(buffer + bytes, &ev))
>> + return -EFAULT;
> Unless the failure is in the very first packet we should tell the user
> how many bytes we have transferred successfully instead of returning
> -EFAULT.
Good point. evdev is also broken in this regard, I'll send a follow-up
patch for that once you are happy with this one. Updated patch is below:
~Ryan
---
diff --git a/drivers/input/misc/uinput.c b/drivers/input/misc/uinput.c
index a0a4bba..92ca2c5 100644
--- a/drivers/input/misc/uinput.c
+++ b/drivers/input/misc/uinput.c
@@ -434,16 +434,20 @@ static ssize_t uinput_inject_event(struct uinput_device *u
const char __user *buffer, size_t count)
{
struct input_event ev;
+ size_t bytes = 0;
- if (count < input_event_size())
+ if (count != 0 && count < input_event_size())
return -EINVAL;
- if (input_event_from_user(buffer, &ev))
- return -EFAULT;
+ while (bytes + input_event_size() <= count) {
+ if (input_event_from_user(buffer + bytes, &ev))
+ return bytes ?: -EFAULT;
- input_event(udev->dev, ev.type, ev.code, ev.value);
+ input_event(udev->dev, ev.type, ev.code, ev.value);
+ bytes += input_event_size();
+ }
- return input_event_size();
+ return bytes;
}
static ssize_t uinput_write(struct file *file, const char __user *buffer,
^ permalink raw reply related [flat|nested] 6+ messages in thread
end of thread, other threads:[~2013-09-11 0:29 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-09-10 23:32 [PATCH 1/2] uinput: Support injecting multiple events in one write() call Ryan Mallon
2013-09-10 23:32 ` [PATCH 2/2] uinput: Use input_inject_event in uinput_inject_event Ryan Mallon
2013-09-11 0:12 ` Dmitry Torokhov
2013-09-11 0:26 ` Ryan Mallon
2013-09-11 0:14 ` [PATCH 1/2] uinput: Support injecting multiple events in one write() call Dmitry Torokhov
2013-09-11 0:29 ` Ryan Mallon
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).