[libvirt] [PATCH] do not report OOM error when prepareCall() failed
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; } -- 1.7.1
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@redhat.com +1-801-349-2682 Libvirt virtualization library http://libvirt.org
participants (2)
-
Eric Blake -
Wen Congyang