From: Laura Abbott <labbott@redhat.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [patch] staging: android: ion: Fix error handling in ion_query_heaps()
Date: Thu, 13 Oct 2016 00:12:42 +0000 [thread overview]
Message-ID: <81184792-900c-d0a1-1a55-d8505a3a3e90@redhat.com> (raw)
In-Reply-To: <20161012124940.GA23933@mwanda>
On 10/12/2016 05:49 AM, Dan Carpenter wrote:
> copy_to_user() returns the number of bytes remaining to be copied. We
> want to return -EFAULT here instead. Also there seems like no point
> in continuing the loop if copy_to_user() fails.
>
> Fixes: 02b23803c6af ('staging: android: ion: Add ioctl to query available heaps')
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> ---
> The error handling still might be wrong here. Do we really want to
> change query->cnt? Please review.
>
> diff --git a/drivers/staging/android/ion/ion.c b/drivers/staging/android/ion/ion.c
> index 396ded5..4cec0b2 100644
> --- a/drivers/staging/android/ion/ion.c
> +++ b/drivers/staging/android/ion/ion.c
> @@ -1187,8 +1187,10 @@ int ion_query_heaps(struct ion_client *client, struct ion_heap_query *query)
> hdata.type = heap->type;
> hdata.heap_id = heap->id;
>
> - ret = copy_to_user(&buffer[cnt],
> - &hdata, sizeof(hdata));
> + if (copy_to_user(&buffer[cnt], &hdata, sizeof(hdata))) {
> + ret = -EFAULT;
> + break;
> + }
>
> cnt++;
> if (cnt >= max_cnt)
>
Yeah, I really butchered the error handling on this. You are correct,
query->cnt shouldn't be updated. break can be changed to 'goto out'.
Thanks,
Laura
prev parent reply other threads:[~2016-10-13 0:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 12:49 [patch] staging: android: ion: Fix error handling in ion_query_heaps() Dan Carpenter
2016-10-13 0:12 ` Laura Abbott [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=81184792-900c-d0a1-1a55-d8505a3a3e90@redhat.com \
--to=labbott@redhat.com \
--cc=kernel-janitors@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