[libvirt] [PATCH 1/2] remote: Fix erroneous usage of constant

John Ferlan jferlan at redhat.com
Tue Oct 4 13:22:24 UTC 2016


The REMOTE_DOMAIN_MEMORY_PARAMETERS_MAX was erroneously used in the
remoteDomainBlockStatsFlags and remoteDomainGetBlockIoTune calls. Change
the constant to be the right one.

Fortunately, all 3 are defined as 16.

Signed-off-by: John Ferlan <jferlan at redhat.com>
---
 src/remote/remote_driver.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/remote/remote_driver.c b/src/remote/remote_driver.c
index 3b8b796..f6c6940 100644
--- a/src/remote/remote_driver.c
+++ b/src/remote/remote_driver.c
@@ -1762,7 +1762,7 @@ remoteDomainBlockStatsFlags(virDomainPtr domain,
     /* Deserialize the result. */
     if (virTypedParamsDeserialize((virTypedParameterRemotePtr) ret.params.params_val,
                                   ret.params.params_len,
-                                  REMOTE_DOMAIN_MEMORY_PARAMETERS_MAX,
+                                  REMOTE_DOMAIN_BLOCK_STATS_PARAMETERS_MAX,
                                   &params,
                                   nparams) < 0)
         goto cleanup;
@@ -2869,7 +2869,7 @@ static int remoteDomainGetBlockIoTune(virDomainPtr domain,
 
     if (virTypedParamsDeserialize((virTypedParameterRemotePtr) ret.params.params_val,
                                   ret.params.params_len,
-                                  REMOTE_DOMAIN_MEMORY_PARAMETERS_MAX,
+                                  REMOTE_DOMAIN_BLOCK_IO_TUNE_PARAMETERS_MAX,
                                   &params,
                                   nparams) < 0)
         goto cleanup;
-- 
2.7.4




More information about the libvir-list mailing list