xen/page_alloc: Distinguish different errors from assign_pages()

assign_pages() has a return type of int, but only returns 0 or -1.  As there
are two distinct failure cases, return a more meaningful error.

All caller currently use its boolean nature, so there is no resulting
change (yet).

Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Reviewed-by: Jan Beulich <jbeulich@suse.com>
This commit is contained in:
Andrew Cooper committed 2016-06-30 12:31:30 +01:00
1 parent 3572f2fa7b
commit 8cf167595f
1 file changed
+7 -7
+7 -7
View File
@@ -1740,6 +1740,7 @@ int assign_pages(
unsigned int order,
unsigned int memflags)
{
int rc = 0;
unsigned long i;
spin_lock(&d->page_alloc_lock);
@@ -1748,7 +1749,8 @@ int assign_pages(
{
gdprintk(XENLOG_INFO, "Cannot assign page to domain%d -- dying.\n",
d->domain_id);
goto fail;
rc = -EINVAL;
goto out;
}
if ( !(memflags & MEMF_no_refcount) )
@@ -1759,7 +1761,8 @@ int assign_pages(
gprintk(XENLOG_INFO, "Over-allocation for domain %u: "
"%u > %u\n", d->domain_id,
d->tot_pages + (1 << order), d->max_pages);
goto fail;
rc = -E2BIG;
goto out;
}
if ( unlikely(d->tot_pages == 0) )
@@ -1778,12 +1781,9 @@ int assign_pages(
page_list_add_tail(&pg[i], &d->page_list);
}
out:
spin_unlock(&d->page_alloc_lock);
return 0;
fail:
spin_unlock(&d->page_alloc_lock);
return -1;
return rc;
}
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.