From: Juergen Gross <jgross@suse.com>
To: Pan Bian <bianpan2016@163.com>,
David Vrabel <david.vrabel@citrix.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
xen-devel@lists.xenproject.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1 v2] xen: set error code on failures
Date: Mon, 5 Dec 2016 09:58:50 +0100 [thread overview]
Message-ID: <5ef5e6ee-876b-ff02-6678-13e011fca4cd@suse.com> (raw)
In-Reply-To: <1480926185-19926-1-git-send-email-bianpan2016@163.com>
On 05/12/16 09:23, Pan Bian wrote:
> Variable rc is reset in the loop, and its value will be non-negative
> during the second and after repeat of the loop. If it fails to allocate
> memory then, it may return a non-negative integer, which indicates no
> error. This patch fixes the bug, assigning "-ENOMEM" to rc when
> kzalloc() or alloc_page() returns NULL, and removing the initialization
> of rc outside of the loop.
>
> v1 is reviewed by: Juergen Gross <jgross@suse.com>
Not being a real problem in this case I prefer spelling out explicit
"Acked-by:" or "Reviewed-by:" tags myself.
So for this version you can have:
Reviewed-by: Juergen Gross <jgross@suse.com>
Juergen
>
> Signed-off-by: Pan Bian <bianpan2016@163.com>
> ---
> drivers/xen/gntalloc.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/xen/gntalloc.c b/drivers/xen/gntalloc.c
> index 7a47c4c..1bf55a3 100644
> --- a/drivers/xen/gntalloc.c
> +++ b/drivers/xen/gntalloc.c
> @@ -127,18 +127,21 @@ static int add_grefs(struct ioctl_gntalloc_alloc_gref *op,
> struct gntalloc_gref *gref, *next;
>
> readonly = !(op->flags & GNTALLOC_FLAG_WRITABLE);
> - rc = -ENOMEM;
> for (i = 0; i < op->count; i++) {
> gref = kzalloc(sizeof(*gref), GFP_KERNEL);
> - if (!gref)
> + if (!gref) {
> + rc = -ENOMEM;
> goto undo;
> + }
> list_add_tail(&gref->next_gref, &queue_gref);
> list_add_tail(&gref->next_file, &queue_file);
> gref->users = 1;
> gref->file_index = op->index + i * PAGE_SIZE;
> gref->page = alloc_page(GFP_KERNEL|__GFP_ZERO);
> - if (!gref->page)
> + if (!gref->page) {
> + rc = -ENOMEM;
> goto undo;
> + }
>
> /* Grant foreign access to the page. */
> rc = gnttab_grant_foreign_access(op->domid,
>
next prev parent reply other threads:[~2016-12-05 9:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 8:23 Pan Bian
2016-12-05 8:58 ` Juergen Gross [this message]
2016-12-08 6:57 ` Juergen Gross
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=5ef5e6ee-876b-ff02-6678-13e011fca4cd@suse.com \
--to=jgross@suse.com \
--cc=bianpan2016@163.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xen-devel@lists.xenproject.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®