From: Wen Congyang <wency@cn.fujitsu.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
xen devel <xen-devel@lists.xen.org>
Cc: Shriram Rajagopalan <rshriram@cs.ubc.ca>,
Changlong Xie <xiecl.fnst@cn.fujitsu.com>,
Yang Hongyang <hongyang.yang@easystack.cn>
Subject: Re: [PATCH 3/5] tools/libxc: don't send end record if remus fails
Date: Thu, 31 Dec 2015 08:49:49 +0800 [thread overview]
Message-ID: <56847BAD.60603@cn.fujitsu.com> (raw)
In-Reply-To: <5683BBE0.1050006@citrix.com>
On 12/30/2015 07:11 PM, Andrew Cooper wrote:
> On 30/12/2015 01:39, Wen Congyang wrote:
>> Signed-off-by: Wen Congyang <wency@cn.fujitsu.com>
>
> Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
>
> While looking at this code, what about error handling for the postcopy() callback just out of context?
We don't handle it now. IIRC, migration v1 doesn't handle it to. I think we should
handle it.
Thanks
Wen Congyang
>
>> ---
>> tools/libxc/xc_sr_save.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/tools/libxc/xc_sr_save.c b/tools/libxc/xc_sr_save.c
>> index cefcef5..76ebb34 100644
>> --- a/tools/libxc/xc_sr_save.c
>> +++ b/tools/libxc/xc_sr_save.c
>> @@ -790,7 +790,7 @@ static int save(struct xc_sr_context *ctx, uint16_t guest_type)
>> rc = ctx->save.callbacks->checkpoint(ctx->save.callbacks->data);
>> if ( rc <= 0 )
>> - ctx->save.checkpointed = false;
>> + goto err;
>> }
>> } while ( ctx->save.checkpointed );
>>
>
>
>
> .
>
next prev parent reply other threads:[~2015-12-31 0:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 1:39 [PATCH 0/5] migration/remus: bug fix and cleanup Wen Congyang
2015-12-30 1:39 ` [PATCH 1/5] remus: don't call stream_continue() when doing failover Wen Congyang
2015-12-30 10:43 ` Andrew Cooper
2015-12-30 1:39 ` [PATCH 2/5] remus: don't write xenstore data if it fails Wen Congyang
2015-12-30 10:47 ` Andrew Cooper
2015-12-31 1:00 ` Wen Congyang
2015-12-30 1:39 ` [PATCH 3/5] tools/libxc: don't send end record if remus fails Wen Congyang
2015-12-30 11:11 ` Andrew Cooper
2015-12-31 0:49 ` Wen Congyang [this message]
2015-12-30 1:39 ` [PATCH 4/5] tools/libxl: remove unused function libxl__domain_save_device_model() Wen Congyang
2015-12-30 1:39 ` [PATCH 5/5] Allow all user to create a file under the directory /var/lib/xen Wen Congyang
2015-12-30 4:11 ` Doug Goldstein
2015-12-30 5:25 ` Wen Congyang
2015-12-30 11:00 ` Andrew Cooper
2016-01-25 20:36 ` Konrad Rzeszutek Wilk
2016-01-26 0:00 ` Andrew Cooper
2016-01-26 9:30 ` Ian Campbell
2016-01-26 17:15 ` Stefano Stabellini
2016-01-27 9:48 ` Ian Campbell
2015-12-30 10:38 ` [PATCH 0/5] migration/remus: bug fix and cleanup Andrew Cooper
2015-12-31 0:48 ` Wen Congyang
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=56847BAD.60603@cn.fujitsu.com \
--to=wency@cn.fujitsu.com \
--cc=andrew.cooper3@citrix.com \
--cc=hongyang.yang@easystack.cn \
--cc=rshriram@cs.ubc.ca \
--cc=xen-devel@lists.xen.org \
--cc=xiecl.fnst@cn.fujitsu.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).