From: "Henrik Rydberg" <rydberg@euromail.se>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Peter Korsgaard <jacmet@sunsite.dk>,
linux-input@vger.kernel.org, baruch@tkos.co.il
Subject: Re: [PATCHv2] evdev: fix evdev_write return value on partial writes
Date: Fri, 4 Feb 2011 11:24:05 +0100 [thread overview]
Message-ID: <20110204102405.GA1567@polaris.bitmath.org> (raw)
In-Reply-To: <20110204084652.GB13046@core.coreip.homeip.net>
> > I doubt this will introduce any regressions (but you never know). The
> > only situation I can see is if userspace would fill out a proper struct
> > input_dev but use a wrong (too small) length in the write call. We used
> > to accept these, but with the patch here it will -EINVAL.
>
> I think that returning -EINVAL is good idea, so I am going to apply it.
> I also think we can change this loop to do-while kind since we already
> checked there enough space for an event.
The code below will return -EINVAL even if some parts of the buffer
was successfully read, though.
>
> --
> Dmitry
>
>
> Input: evdev - fix evdev_write return value on partial writes
>
> From: Peter Korsgaard <jacmet@sunsite.dk>
>
> As was recently brought up on the busybox list
> (http://lists.busybox.net/pipermail/busybox/2011-January/074565.html),
> evdev_write doesn't properly check the count argument, which will
> lead to a return value > count on partial writes if the remaining bytes
> are accessible - causing userspace confusion.
>
> Fix it by only handling each full input_event structure and return -EINVAL
> if less than 1 struct was written, similar to how it is done in evdev_read.
>
> Reported-by: Baruch Siach <baruch@tkos.co.il>
> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
> Signed-off-by: Dmitry Torokhov <dtor@mail.ru>
> ---
>
> drivers/input/evdev.c | 10 ++++++----
> 1 files changed, 6 insertions(+), 4 deletions(-)
>
>
> diff --git a/drivers/input/evdev.c b/drivers/input/evdev.c
> index c8471a2..7f42d3a 100644
> --- a/drivers/input/evdev.c
> +++ b/drivers/input/evdev.c
> @@ -321,6 +321,9 @@ static ssize_t evdev_write(struct file *file, const char __user *buffer,
> struct input_event event;
> int retval;
Alternatively,
size_t num_written = 0;
int ret = 0;
>
> + if (count < input_event_size())
> + return -EINVAL;
> +
> retval = mutex_lock_interruptible(&evdev->mutex);
> if (retval)
> return retval;
> @@ -330,17 +333,16 @@ static ssize_t evdev_write(struct file *file, const char __user *buffer,
> goto out;
> }
>
> - while (retval < count) {
while (num_written + input_event_size() <= count) {
> -
> + do {
> if (input_event_from_user(buffer + retval, &event)) {
> retval = -EFAULT;
ret = -EFAULT;
> goto out;
> }
> + retval += input_event_size();
num_written += input_event_size();
>
> input_inject_event(&evdev->handle,
> event.type, event.code, event.value);
> - retval += input_event_size();
> - }
> + } while (retval + input_event_size() <= count);
>
> out:
> mutex_unlock(&evdev->mutex);
return ret ? ret : num_written;
Thanks,
Henrik
next prev parent reply other threads:[~2011-02-04 10:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-27 10:03 [PATCHv2] evdev: fix evdev_write return value on partial writes Peter Korsgaard
2011-01-27 11:02 ` Henrik Rydberg
2011-01-27 11:21 ` Peter Korsgaard
2011-01-27 11:26 ` Baruch Siach
2011-01-27 11:29 ` Peter Korsgaard
2011-01-27 11:47 ` Henrik Rydberg
2011-01-27 12:04 ` Peter Korsgaard
2011-01-27 12:26 ` Henrik Rydberg
2011-01-27 12:43 ` Peter Korsgaard
2011-02-04 8:46 ` Dmitry Torokhov
2011-02-04 10:24 ` Henrik Rydberg [this message]
2011-02-04 11:00 ` Peter Korsgaard
2011-02-04 11:23 ` Henrik Rydberg
2011-02-04 17:15 ` Dmitry Torokhov
2011-02-04 17:22 ` Henrik Rydberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110204102405.GA1567@polaris.bitmath.org \
--to=rydberg@euromail.se \
--cc=baruch@tkos.co.il \
--cc=dmitry.torokhov@gmail.com \
--cc=jacmet@sunsite.dk \
--cc=linux-input@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).