From: Peter Korsgaard <jacmet@sunsite.dk>
To: Henrik Rydberg <rydberg@euromail.se>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input@vger.kernel.org, baruch@tkos.co.il
Subject: Re: [PATCHv2] evdev: fix evdev_write return value on partial writes
Date: Fri, 04 Feb 2011 12:00:28 +0100 [thread overview]
Message-ID: <877hdgrrn7.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20110204102405.GA1567@polaris.bitmath.org> (Henrik Rydberg's message of "Fri, 4 Feb 2011 11:24:05 +0100")
>>>>> "Henrik" == Henrik Rydberg <rydberg@euromail.se> writes:
Hi,
>> 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.
Henrik> The code below will return -EINVAL even if some parts of the buffer
Henrik> was successfully read, though.
You mean written? I don't see that. The only place we return -EINVAL is
at the initial check.
>> --- 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;
Henrik> Alternatively,
Henrik> size_t num_written = 0;
Henrik> int ret = 0;
Any reason for this bigger change? It's imho pretty clear as is. I don't
see any functional change from your version.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2011-02-04 11:00 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
2011-02-04 11:00 ` Peter Korsgaard [this message]
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=877hdgrrn7.fsf@macbook.be.48ers.dk \
--to=jacmet@sunsite.dk \
--cc=baruch@tkos.co.il \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=rydberg@euromail.se \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.