commit a1bb5dd169f4e47690a3b53c64692808472171a7
author Anthony PERARD <anthony.perard@citrix.com> Mon Mar 11 12:34:39 2024 +0000
committer Peter Xu <peterx@redhat.com> Mon Mar 11 14:41:41 2024 -0400
tree fbdc059b229fcbe25ae0c0b206097d3c5f43b3de
parent 47293c922cb4d70aae5b8100936ffc624d2a4076

migration: Fix format in error message

In file_write_ramblock_iov(), "offset" is "uintptr_t" and not
"ram_addr_t". While usually they are both equivalent, this is not the
case with CONFIG_XEN_BACKEND.

Use the right format. This will fix build on 32-bit.

Fixes: f427d90b9898 ("migration/multifd: Support outgoing mapped-ram stream format")
Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>
Link: https://lore.kernel.org/r/20240311123439.16844-1-anthony.perard@citrix.com
Signed-off-by: Peter Xu <peterx@redhat.com>

migration/file.c

diff --git a/migration/file.c b/migration/file.c
index 164b079..5054a60 100644
--- a/migration/file.c
+++ b/migration/file.c
@@ -191,7 +191,7 @@
          */
         offset = (uintptr_t) iov[slice_idx].iov_base - (uintptr_t) block->host;
         if (offset >= block->used_length) {
-            error_setg(errp, "offset " RAM_ADDR_FMT
+            error_setg(errp, "offset %" PRIxPTR
                        "outside of ramblock %s range", offset, block->idstr);
             ret = -1;
             break;