Re: [PATCH] do not report OOM error when prepareCall() failed

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 03/21/2011 12:29 AM, Wen Congyang wrote:
> We have reported error in the function prepareCall(), and
> the error is not only OOM error. So we should not report
> OOM error in the function call() when prepareCall() failed.
> 
> ---
>  src/remote/remote_driver.c |    1 -
>  1 files changed, 0 insertions(+), 1 deletions(-)
> 
> diff --git a/src/remote/remote_driver.c b/src/remote/remote_driver.c
> index b844d9a..5f3e288 100644
> --- a/src/remote/remote_driver.c
> +++ b/src/remote/remote_driver.c
> @@ -10832,7 +10832,6 @@ call (virConnectPtr conn, struct private_data *priv,
>                             ret_filter, ret);
>  
>      if (!thiscall) {
> -        virReportOOMError();
>          return -1;

ACK and pushed.

-- 
Eric Blake   eblake@xxxxxxxxxx    +1-801-349-2682
Libvirt virtualization library http://libvirt.org

Attachment: signature.asc
Description: OpenPGP digital signature

--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list

[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]