From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Tuguoyi <tu.guoyi@h3c.com>, berrange@redhat.com
Cc: tuguoyi@outlook.com, qemu-devel@nongnu.org,
Juan Quintela <quintela@redhat.com>
Subject: Re: [PATCH 2/2] savevm: Delete snapshots just created in case of error
Date: Thu, 17 Dec 2020 15:38:10 +0000 [thread overview]
Message-ID: <20201217153810.GJ4117@work-vm> (raw)
In-Reply-To: <1607410416-13563-3-git-send-email-tu.guoyi@h3c.com>
* Tuguoyi (tu.guoyi@h3c.com) wrote:
> bdrv_all_create_snapshot() can fails with some snapshots created,
> so it's better to delete those snapshots before returns to the caller
>
> Signed-off-by: Tuguoyi <tu.guoyi@h3c.com>
This makes sense to me,
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> ---
> migration/savevm.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/migration/savevm.c b/migration/savevm.c
> index 601b514..4a18c9d 100644
> --- a/migration/savevm.c
> +++ b/migration/savevm.c
> @@ -2833,6 +2833,7 @@ int save_snapshot(const char *name, Error **errp)
> if (ret < 0) {
> error_setg(errp, "Error while creating snapshot on '%s'",
> bdrv_get_device_or_node_name(bs));
> + bdrv_all_delete_snapshot(sn->name, &bs, NULL);
> goto the_end;
> }
>
> --
> 2.7.4
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
prev parent reply other threads:[~2020-12-17 15:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 6:53 [PATCH 0/2] savevm: Delete stale snapshots in save_snapshot() Tuguoyi
2020-12-08 6:53 ` [PATCH 1/2] savevm: Remove dead code " Tuguoyi
2020-12-17 15:27 ` Dr. David Alan Gilbert
2020-12-17 16:14 ` Denis V. Lunev
2020-12-17 17:32 ` Dr. David Alan Gilbert
2020-12-08 6:53 ` [PATCH 2/2] savevm: Delete snapshots just created in case of error Tuguoyi
2020-12-17 15:38 ` Dr. David Alan Gilbert [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=20201217153810.GJ4117@work-vm \
--to=dgilbert@redhat.com \
--cc=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=tu.guoyi@h3c.com \
--cc=tuguoyi@outlook.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).