summaryrefslogtreecommitdiff
path: root/gdb-xml
diff options
context:
space:
mode:
authorzhanghailiang <zhang.zhanghailiang@huawei.com>2017-04-19 09:15:32 +0800
committerPaolo Bonzini <pbonzini@redhat.com>2017-05-03 12:29:40 +0200
commitb19456dd0ea4eb418ad093f092adbb882be13054 (patch)
tree8afc0cde99c206b002f5bc3c4f5b6c6201c67364 /gdb-xml
parent6103451aeb749e92bf7d730429985189c6921c32 (diff)
downloadqemu-b19456dd0ea4eb418ad093f092adbb882be13054.tar.gz
char: Fix removing wrong GSource that be found by fd_in_tag
We use fd_in_tag to find a GSource, fd_in_tag is return value of g_source_attach(GSource *source, GMainContext *context), the return value is unique only in the same context, so we may get the same values with different 'context' parameters. It is no problem to find the right fd_in_tag by using g_main_context_find_source_by_id(GMainContext *context, guint source_id) while there is only one default main context. But colo-compare tries to create/use its own context, and if we pass wrong 'context' parameter with right fd_in_tag, we will find a wrong GSource to handle. We tried to fix the related codes in commit b43decb015a6efeb9e3cdbdb80f6547ad7248a4c, but it didn't fix the bug completely, because we still have some codes didn't pass *right* context parameter for remove_fd_in_watch(). Let's fix it by record the GSource directly instead of fd_in_tag. Signed-off-by: zhanghailiang <zhang.zhanghailiang@huawei.com> Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com> Message-Id: <1492564532-91680-1-git-send-email-zhang.zhanghailiang@huawei.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'gdb-xml')
0 files changed, 0 insertions, 0 deletions