From: Peter Xu <peterx@redhat.com>
To: Stefan Weil <sw@weilnetz.de>
Cc: Fabiano Rosas <farosas@suse.de>,
qemu-devel@nongnu.org, qemu-trivial@nongnu.org
Subject: Re: [PATCH-for-10.2] Fix order of function arguments
Date: Tue, 9 Dec 2025 14:03:56 -0500 [thread overview]
Message-ID: <aThynO5EgO_YF7Pz@x1.local> (raw)
In-Reply-To: <20251209125049.764095-1-sw@weilnetz.de>
On Tue, Dec 09, 2025 at 01:50:49PM +0100, Stefan Weil via wrote:
> This fixes a compiler error when higher warning levels are enabled:
>
> ../migration/postcopy-ram.c: In function ‘postcopy_temp_pages_setup’:
> ../migration/postcopy-ram.c:1483:50: error: ‘g_malloc0_n’ sizes specified with ‘sizeof’ in the earlier argument and not in the later argument [-Werror=calloc-transposed-args]
> 1483 | mis->postcopy_tmp_pages = g_malloc0_n(sizeof(PostcopyTmpPage), channels);
> | ^~~~~~~~~~~~~~~
> ../migration/postcopy-ram.c:1483:50: note: earlier argument should specify number of elements, later size of each element
>
> Avoid also a related int/unsigned mismatch by fixing the type of
> two local variables.
>
> Signed-off-by: Stefan Weil <sw@weilnetz.de>
> ---
> migration/postcopy-ram.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/migration/postcopy-ram.c b/migration/postcopy-ram.c
> index 3f98dcb6fd..8bef0192aa 100644
> --- a/migration/postcopy-ram.c
> +++ b/migration/postcopy-ram.c
> @@ -1467,7 +1467,8 @@ retry:
> static int postcopy_temp_pages_setup(MigrationIncomingState *mis)
> {
> PostcopyTmpPage *tmp_page;
> - int err, i, channels;
> + int err;
> + unsigned i, channels;
> void *temp_page;
>
> if (migrate_postcopy_preempt()) {
> @@ -1479,7 +1480,7 @@ static int postcopy_temp_pages_setup(MigrationIncomingState *mis)
> }
>
> channels = mis->postcopy_channels;
> - mis->postcopy_tmp_pages = g_malloc0_n(sizeof(PostcopyTmpPage), channels);
> + mis->postcopy_tmp_pages = g_malloc0_n(channels, sizeof(PostcopyTmpPage));
>
> for (i = 0; i < channels; i++) {
> tmp_page = &mis->postcopy_tmp_pages[i];
> --
> 2.47.3
>
Thanks for the patch, I'll wait for v2 per others' comments (or if Laurent
would pick it up).
Please also consider adding a prefix ("migration:") the subject.
--
Peter Xu
prev parent reply other threads:[~2025-12-09 19:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-09 12:50 [PATCH-for-10.2] Fix order of function arguments Stefan Weil via
2025-12-09 12:50 ` Stefan Weil via
2025-12-09 12:59 ` Laurent Vivier
2025-12-09 13:03 ` Philippe Mathieu-Daudé
2025-12-09 13:09 ` Daniel P. Berrangé
2025-12-09 14:17 ` Philippe Mathieu-Daudé
2025-12-09 21:17 ` Stefan Weil via
2025-12-09 19:03 ` Peter Xu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aThynO5EgO_YF7Pz@x1.local \
--to=peterx@redhat.com \
--cc=farosas@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=sw@weilnetz.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.