From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: qemu-devel@nongnu.org, jemmy858585@gmail.com,
quintela@redhat.com, peterx@redhat.com
Subject: Re: [Qemu-devel] [PATCH] migration/rdma: unegister fd handler
Date: Wed, 23 Jan 2019 11:44:48 +0000 [thread overview]
Message-ID: <20190123114448.GB5771@work-vm> (raw)
In-Reply-To: <20190122173111.29821-1-dgilbert@redhat.com>
* Dr. David Alan Gilbert (git) (dgilbert@redhat.com) wrote:
> From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
>
> Unregister the fd handler before we destroy the channel,
> otherwise we've got a race where we might land in the
> fd handler just as we're closing the device.
>
> (The race is quite data dependent, you just have to have
> the right set of devices for it to trigger).
>
> Corresponds to RH bz: https://bugzilla.redhat.com/show_bug.cgi?id=1666601
>
> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Queued
> ---
> migration/rdma.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/migration/rdma.c b/migration/rdma.c
> index 9b2e7e10aa..54a3c11540 100644
> --- a/migration/rdma.c
> +++ b/migration/rdma.c
> @@ -2321,6 +2321,7 @@ static void qemu_rdma_cleanup(RDMAContext *rdma)
> rdma->connected = false;
> }
>
> + qemu_set_fd_handler(rdma->channel->fd, NULL, NULL, NULL);
> g_free(rdma->dest_blocks);
> rdma->dest_blocks = NULL;
>
> --
> 2.20.1
>
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2019-01-23 11:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 17:31 [Qemu-devel] [PATCH] migration/rdma: unegister fd handler Dr. David Alan Gilbert (git)
2019-01-23 8:13 ` Peter Xu
2019-01-23 9:31 ` Dr. David Alan Gilbert
2019-01-23 11:44 ` Dr. David Alan Gilbert [this message]
2019-01-23 18:30 ` Philippe Mathieu-Daudé
2019-01-23 18:31 ` Dr. David Alan Gilbert
2019-02-14 18:08 ` Peter Maydell
2019-02-14 18:37 ` Dr. David Alan Gilbert
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=20190123114448.GB5771@work-vm \
--to=dgilbert@redhat.com \
--cc=jemmy858585@gmail.com \
--cc=peterx@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.