From: Colin Ian King <colin.king@canonical.com>
To: Jeremy Kerr <jk@ozlabs.org>, Joel Stanley <joel@jms.id.au>,
Alistar Popple <alistair@popple.id.au>,
Eddie James <eajames@linux.ibm.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linux-fsi@lists.ozlabs.org
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [PATCH v2] fsi: fix bogus error returns from cfam_read and cfam_write
Date: Fri, 29 Nov 2019 09:03:50 +0000 [thread overview]
Message-ID: <a5e2570f-222b-5633-af67-6cf5650a741f@canonical.com> (raw)
In-Reply-To: <20191129032429.817-1-jk@ozlabs.org>
On 29/11/2019 03:24, Jeremy Kerr wrote:
> Based on a static analysis report and original patch from Colin Ian King
> <colin.king@canonical.com>.
>
> Currently, we may drop error values from cfam_read and cfam_write. This
> change returns the actual error on failure, but a partial read/write will
> take precedence.
>
> Addresses-Coverity: ("Unused value")
> Fixes: d1dcd6782576 ("fsi: Add cfam char devices")
> Reported-by: Colin Ian King <colin.king@canonical.com>
> Signed-off-by: Jeremy Kerr <jk@ozlabs.org>
>
> ---
> Colin: thanks for the report and patch. I think this is a more complete
> fix, as we want to preseve any partial read/write status if a failure
> happens mid-way through an operation. Let me know if you (or the
> coverity analysis) have any feedback.
Looks good to me. Thanks Jeremy.
>
> ---
>
> drivers/fsi/fsi-core.c | 32 ++++++++++++++++++++++----------
> 1 file changed, 22 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/fsi/fsi-core.c b/drivers/fsi/fsi-core.c
> index 71c6f9fef648..3158a78c2e94 100644
> --- a/drivers/fsi/fsi-core.c
> +++ b/drivers/fsi/fsi-core.c
> @@ -699,6 +699,8 @@ static ssize_t cfam_read(struct file *filep, char __user *buf, size_t count,
> if (off > 0xffffffff || count > 0xffffffff || off + count > 0xffffffff)
> return -EINVAL;
>
> + rc = 0;
> +
> for (total_len = 0; total_len < count; total_len += read_len) {
> __be32 data;
>
> @@ -707,18 +709,22 @@ static ssize_t cfam_read(struct file *filep, char __user *buf, size_t count,
>
> rc = fsi_slave_read(slave, off, &data, read_len);
> if (rc)
> - goto fail;
> + break;
> rc = copy_to_user(buf + total_len, &data, read_len);
> if (rc) {
> rc = -EFAULT;
> - goto fail;
> + break;
> }
> off += read_len;
> }
> - rc = count;
> - fail:
> +
> + /* if we've read any data, we want that to be returned in
> + * preference to an error state */
> + if (total_len)
> + rc = total_len;
> +
> *offset = off;
> - return count;
> + return rc;
> }
>
> static ssize_t cfam_write(struct file *filep, const char __user *buf,
> @@ -736,6 +742,8 @@ static ssize_t cfam_write(struct file *filep, const char __user *buf,
> if (off > 0xffffffff || count > 0xffffffff || off + count > 0xffffffff)
> return -EINVAL;
>
> + rc = 0;
> +
> for (total_len = 0; total_len < count; total_len += write_len) {
> __be32 data;
>
> @@ -745,17 +753,21 @@ static ssize_t cfam_write(struct file *filep, const char __user *buf,
> rc = copy_from_user(&data, buf + total_len, write_len);
> if (rc) {
> rc = -EFAULT;
> - goto fail;
> + break;
> }
> rc = fsi_slave_write(slave, off, &data, write_len);
> if (rc)
> - goto fail;
> + break;
> off += write_len;
> }
> - rc = count;
> - fail:
> +
> + /* if we've written any data, we want to indicate that partial write
> + * instead of any mid-stream error */
> + if (total_len)
> + rc = total_len;
> +
> *offset = off;
> - return count;
> + return rc;
> }
>
> static loff_t cfam_llseek(struct file *file, loff_t offset, int whence)
>
prev parent reply other threads:[~2019-11-29 9:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-22 23:31 [PATCH] fsi: fix bogos " Colin King
2019-11-28 22:32 ` Andrew Jeffery
2019-11-28 23:20 ` Joel Stanley
2019-11-29 3:24 ` [PATCH] [PATCH v2] fsi: fix bogus " Jeremy Kerr
2019-11-29 9:03 ` Colin Ian King [this message]
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=a5e2570f-222b-5633-af67-6cf5650a741f@canonical.com \
--to=colin.king@canonical.com \
--cc=alistair@popple.id.au \
--cc=benh@kernel.crashing.org \
--cc=eajames@linux.ibm.com \
--cc=jk@ozlabs.org \
--cc=joel@jms.id.au \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-fsi@lists.ozlabs.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®