From: "Michael R. Hines" <mrhines@linux.vnet.ibm.com>
To: arei.gonglei@huawei.com, qemu-devel@nongnu.org
Cc: weidong.huang@huawei.com, quintela@redhat.com,
dgilbert@redhat.com, owasserm@redhat.com, mrhines@us.ibm.com,
pbonzini@redhat.com, Mo Yuxiang <Moyuxiang@huawei.com>
Subject: Re: [Qemu-devel] [PATCH] rdma: Fix block during rdma migration
Date: Tue, 01 Apr 2014 08:42:15 +0800 [thread overview]
Message-ID: <533A0B67.6010308@linux.vnet.ibm.com> (raw)
In-Reply-To: <1396078745-5584-1-git-send-email-arei.gonglei@huawei.com>
On 03/29/2014 03:39 PM, arei.gonglei@huawei.com wrote:
> From: Mo Yuxiang <Moyuxiang@huawei.com>
>
> If the networking break or there's something wrong with rdma
> device(ib0 with no IP) during rdma migration, the main_loop of
> qemu will be blocked in rdma_destroy_id. I add rdma_ack_cm_event
> to fix this bug.
>
> Signed-off-by: Mo Yuxiang <Moyuxiang@huawei.com>
> Signed-off-by: Gonglei <arei.gonglei@huawei.com>
> ---
> migration-rdma.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/migration-rdma.c b/migration-rdma.c
> index eeb4302..f60749b 100644
> --- a/migration-rdma.c
> +++ b/migration-rdma.c
> @@ -949,6 +949,7 @@ route:
> ERROR(errp, "result not equal to event_addr_resolved %s",
> rdma_event_str(cm_event->event));
> perror("rdma_resolve_addr");
> + rdma_ack_cm_event(cm_event);
> ret = -EINVAL;
> goto err_resolve_get_addr;
> }
Reviewed-by: Michael R. Hines <mrhines@us.ibm.com>
Good catch. =) That's an obvious bug. It looks like I need
to do a much better job of "kill -9" inside the regression
testing scripts - probably i should try killing the migration
prematurely at different periods just to be sure there are
no more places where the connection state is not getting
cleaned up......
- Michael
next prev parent reply other threads:[~2014-04-01 0:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-29 7:39 [Qemu-devel] [PATCH] rdma: Fix block during rdma migration arei.gonglei
2014-04-01 0:42 ` Michael R. Hines [this message]
2014-04-01 1:47 ` Gonglei (Arei)
2014-05-09 4:25 ` Gonglei (Arei)
2014-05-15 0:43 ` Michael R. Hines
2014-05-15 6:47 ` Gonglei (Arei)
2014-05-15 10:08 ` Juan Quintela
-- strict thread matches above, loose matches on Subject: below --
2014-03-17 1:45 Wangyufei (James)
2014-03-14 1:42 Wangyufei (James)
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=533A0B67.6010308@linux.vnet.ibm.com \
--to=mrhines@linux.vnet.ibm.com \
--cc=Moyuxiang@huawei.com \
--cc=arei.gonglei@huawei.com \
--cc=dgilbert@redhat.com \
--cc=mrhines@us.ibm.com \
--cc=owasserm@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=weidong.huang@huawei.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).