From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: QingFeng Hao <haoqf@linux.vnet.ibm.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org, peterx@redhat.com,
borntraeger@de.ibm.com, cornelia.huck@de.ibm.com,
liujbjl@linux.vnet.ibm.com, famz@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 1/1] qemu/migration: fix the double free problem on from_src_file
Date: Wed, 7 Jun 2017 13:18:41 +0100 [thread overview]
Message-ID: <20170607121840.GE2099@work-vm> (raw)
In-Reply-To: <a908cc58-3001-0d8a-0415-887b5cbae4e7@linux.vnet.ibm.com>
* QingFeng Hao (haoqf@linux.vnet.ibm.com) wrote:
>
>
> 在 2017/6/6 20:49, Kevin Wolf 写道:
> > Am 06.06.2017 um 07:24 hat QingFeng Hao geschrieben:
<snip>
> > I can't tell for postcopy_ram_listen_thread() - commit 660819b didn't
> > seem to remove a qemu_fclose() call there, but I can't see one left
> > behind either. Was the file leaked before commit 660819b or am I
> > missing something?
> I don't think so because loadvm_postcopy_handle_listen creates thread
> postcopy_ram_listen_thread
> and passes mis->from_src_file as its arg, which will be closed by
> migration_incoming_state_destroy.
> What confuses me is in the series function calls of qemu_loadvm_state_main
> etc, argument f looks
> to be redundant as mis already contains from_src_file which equals to f.
In postcopy qemu_loadvm_state_main is called with two different file
arguments but the same mis argument; see loadvm_handle_cmd_packaged for
the other case where it's called on a packaged-file blob.
> Furthermore, mis may be
> also redundant as it can be got via migration_incoming_get_current. Thanks!
We keep changing our minds about the preferred style. Sometimes we
think it's best to pass the pointer, sometimes we think it's best
to call get_current.
Dave
> >
> > Kevin
> >
>
> --
> Regards
> QingFeng Hao
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2017-06-07 12:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-06 5:24 [Qemu-devel] [PATCH v2 0/1] qemu/migration: fix the migration bug found by qemu-iotests case 068 QingFeng Hao
2017-06-06 5:24 ` [Qemu-devel] [PATCH v2 1/1] qemu/migration: fix the double free problem on from_src_file QingFeng Hao
2017-06-06 12:49 ` Kevin Wolf
2017-06-06 17:42 ` Dr. David Alan Gilbert
2017-06-07 3:29 ` Peter Xu
2017-06-06 17:57 ` Juan Quintela
2017-06-07 3:18 ` QingFeng Hao
2017-06-07 12:18 ` Dr. David Alan Gilbert [this message]
2017-06-08 5:23 ` QingFeng Hao
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=20170607121840.GE2099@work-vm \
--to=dgilbert@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=famz@redhat.com \
--cc=haoqf@linux.vnet.ibm.com \
--cc=kwolf@redhat.com \
--cc=liujbjl@linux.vnet.ibm.com \
--cc=peterx@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).