qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: David Edmondson <david.edmondson@oracle.com>
Cc: qemu-devel@nongnu.org, Juan Quintela <quintela@redhat.com>
Subject: Re: [PATCH] migration: Report the error returned when save_live_iterate fails
Date: Wed, 15 Dec 2021 19:38:10 +0000	[thread overview]
Message-ID: <YbpEIorKvJnOcCqy@work-vm> (raw)
In-Reply-To: <20211215141437.1238403-1-david.edmondson@oracle.com>

* David Edmondson (david.edmondson@oracle.com) wrote:
> Should qemu_savevm_state_iterate() encounter a failure when calling a
> particular save_live_iterate function, report the error code returned
> by the function.
> 
> Signed-off-by: David Edmondson <david.edmondson@oracle.com>
> ---
>  migration/savevm.c | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/migration/savevm.c b/migration/savevm.c
> index d59e976d50..26aac04d91 100644
> --- a/migration/savevm.c
> +++ b/migration/savevm.c
> @@ -1298,8 +1298,9 @@ int qemu_savevm_state_iterate(QEMUFile *f, bool postcopy)
>          save_section_footer(f, se);
>  
>          if (ret < 0) {
> -            error_report("failed to save SaveStateEntry with id(name): %d(%s)",
> -                         se->section_id, se->idstr);
> +            error_report("failed to save SaveStateEntry with id(name): "
> +                         "%d(%s): %d",
> +                         se->section_id, se->idstr, ret);


Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>

>              qemu_file_set_error(f, ret);
>          }
>          if (ret <= 0) {
> -- 
> 2.33.0
> 
> 
-- 
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK



  reply	other threads:[~2021-12-15 19:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-15 14:14 [PATCH] migration: Report the error returned when save_live_iterate fails David Edmondson
2021-12-15 19:38 ` Dr. David Alan Gilbert [this message]
2022-01-26 20:24 ` Juan Quintela

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=YbpEIorKvJnOcCqy@work-vm \
    --to=dgilbert@redhat.com \
    --cc=david.edmondson@oracle.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).