All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Denis V. Lunev" <den@openvz.org>
To: "Li, Liang Z" <liang.z.li@intel.com>
Cc: Amit Shah <amit.shah@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/1] migration: qemu_savevm_state_cleanup becomes mandatory operation
Date: Mon, 9 Nov 2015 09:18:41 +0300	[thread overview]
Message-ID: <56403AC1.2080407@openvz.org> (raw)
In-Reply-To: <F2CBF3009FA73547804AE4C663CAB28E019A1964@shsmsx102.ccr.corp.intel.com>

On 11/09/2015 09:16 AM, Li, Liang Z wrote:
>> On 11/09/2015 08:10 AM, Li, Liang Z wrote:
>>>> since commit
>>>>       commit 94f5a43704129ca4995aa3385303c5ae225bde42
>>>>       Author: Liang Li <liang.z.li@intel.com>
>>>>       Date:   Mon Nov 2 15:37:00 2015 +0800
>>>>
>>>>       migration: defer migration_end & blk_mig_cleanup
>>>>
>>>> when actual .cleanup callbacks calling was removed from complete
>> operations.
>>>> Signed-off-by: Denis V. Lunev <den@openvz.org>
>>>> CC: Paolo Bonzini <pbonzini@redhat.com>
>>>> CC: Juan Quintela <quintela@redhat.com>
>>>> CC: Amit Shah <amit.shah@redhat.com>
>>>> ---
>>>>    migration/savevm.c | 2 +-
>>>>    1 file changed, 1 insertion(+), 1 deletion(-)
>>>>
>>>> diff --git a/migration/savevm.c b/migration/savevm.c index
>> e05158d..9f2230f
>>>> 100644
>>>> --- a/migration/savevm.c
>>>> +++ b/migration/savevm.c
>>>> @@ -942,8 +942,8 @@ static int qemu_savevm_state(QEMUFile *f, Error
>>>> **errp)
>>>>            qemu_savevm_state_complete(f);
>>>>            ret = qemu_file_get_error(f);
>>>>        }
>>>> +    qemu_savevm_state_cleanup();
>>>>        if (ret != 0) {
>>>> -        qemu_savevm_state_cleanup();
>>>>            error_setg_errno(errp, -ret, "Error while writing VM state");
>>>>        }
>>>>        return ret;
>>>> --
>>>> 2.5.0
>>>>
>>> Yes, you are right. Thanks a lot.
>>>
>>> BTW, can this patch fix the regression you reported?
>>>
>>> Reviewed-by: Liang Li <liang.z.li@intel.com>
>>>
>> yes
> Great.  You'd better change the commit message to make it more clear.
>
> Liang
argh.. you are right...

This problem has appeared in the end of big rework
of another problem with snapshots and dataplane.
Sorry that this is not clear that regression is fixed.
I'll resend the patch with better commit message

Den

  reply	other threads:[~2015-11-09  6:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-07 15:20 [Qemu-devel] assert during internal snapshot Denis V. Lunev
2015-11-07 15:40 ` [Qemu-devel] [PATCH 1/1] migration: qemu_savevm_state_cleanup becomes mandatory operation Denis V. Lunev
2015-11-09  4:06   ` Amit Shah
2015-11-09  5:10   ` Li, Liang Z
2015-11-09  6:11     ` Denis V. Lunev
2015-11-09  6:16       ` Li, Liang Z
2015-11-09  6:18         ` Denis V. Lunev [this message]
2015-11-09  8:22           ` Li, Liang Z
2015-11-09  2:28 ` [Qemu-devel] assert during internal snapshot Li, Liang Z
2015-11-09  3:12 ` Li, Liang Z
2015-11-09  3:29 ` Li, Liang Z
2015-11-10 11:00   ` Stefan Hajnoczi
2015-11-10 11:44     ` Denis V. Lunev
2015-11-09  7:24 ` [Qemu-devel] [PATCH for 2.5 v2 1/1] migration: qemu_savevm_state_cleanup becomes mandatory operation Denis V. Lunev
2015-11-09 16:20   ` 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=56403AC1.2080407@openvz.org \
    --to=den@openvz.org \
    --cc=amit.shah@redhat.com \
    --cc=liang.z.li@intel.com \
    --cc=pbonzini@redhat.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 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.