All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: Aadeshveer Singh <aadeshveer07@gmail.com>
Cc: qemu-devel@nongnu.org, farosas@suse.de
Subject: Re: [PATCH] migration: fix implicit integer division in migration_update_counters
Date: Mon, 16 Mar 2026 16:45:30 -0400	[thread overview]
Message-ID: <abhr6oISW2oAcq2q@x1.local> (raw)
In-Reply-To: <20260316134509.157964-1-aadeshveer07@gmail.com>

On Mon, Mar 16, 2026 at 07:15:09PM +0530, Aadeshveer Singh wrote:
> switchover_bw is a uint64_t, so switchover_bw / 1000 results in an
> integer division. This value is then assigned to expected_bw_per_ms
> which is of type double. This results in losing precision and is type
> unsafe. Adding explicit cast ensures floating-point division.
> 
> Signed-off-by: Aadeshveer Singh <aadeshveer07@gmail.com>

Reviewed-by: Peter Xu <peterx@redhat.com>

Thanks,

> ---
>  migration/migration.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/migration/migration.c b/migration/migration.c
> index f949708629..7094080285 100644
> --- a/migration/migration.c
> +++ b/migration/migration.c
> @@ -3134,7 +3134,7 @@ static void migration_update_counters(MigrationState *s,
>           * If the user specified a switchover bandwidth, let's trust the
>           * user so that can be more accurate than what we estimated.
>           */
> -        expected_bw_per_ms = switchover_bw / 1000;
> +        expected_bw_per_ms = (double)switchover_bw / 1000;
>      } else {
>          /* If the user doesn't specify bandwidth, we use the estimated */
>          expected_bw_per_ms = bandwidth;
> -- 
> 2.53.0
> 

-- 
Peter Xu



      reply	other threads:[~2026-03-16 20:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-16 13:45 [PATCH] migration: fix implicit integer division in migration_update_counters Aadeshveer Singh
2026-03-16 20:45 ` 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=abhr6oISW2oAcq2q@x1.local \
    --to=peterx@redhat.com \
    --cc=aadeshveer07@gmail.com \
    --cc=farosas@suse.de \
    --cc=qemu-devel@nongnu.org \
    /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.