qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Corey Bryant <coreyb@linux.vnet.ibm.com>
To: Eric Blake <eblake@redhat.com>
Cc: kwolf@redhat.com, libvir-list@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 3/4] monitor: Prevent removing fd from set during init
Date: Thu, 18 Oct 2012 09:45:51 -0400	[thread overview]
Message-ID: <5080080F.2040903@linux.vnet.ibm.com> (raw)
In-Reply-To: <507E2DD7.3090702@redhat.com>



On 10/17/2012 12:02 AM, Eric Blake wrote:
> On 10/16/2012 12:08 PM, Corey Bryant wrote:
>> If an fd is added to an fd set via the command line, and it is not
>> referenced by another command line option (ie. -drive), then clean
>> it up after QEMU initialization is complete.
>>
>> Signed-off-by: Corey Bryant <coreyb@linux.vnet.ibm.com>
>> ---
>> v3:
>>    - This patch was split into it's own patch in v3
>>      (eblake@redhat.com, kwolf@redhat.com)
>>
>>   monitor.c | 5 +++--
>>   1 file changed, 3 insertions(+), 2 deletions(-)
>
> Reviewed-by: Eric Blake <eblake@redhat.com>
>

Thanks!

>>
>> diff --git a/monitor.c b/monitor.c
>> index 5d5de41..0dae7ac 100644
>> --- a/monitor.c
>> +++ b/monitor.c
>> @@ -2105,8 +2105,9 @@ static void monitor_fdset_cleanup(MonFdset *mon_fdset)
>>       MonFdsetFd *mon_fdset_fd_next;
>>
>>       QLIST_FOREACH_SAFE(mon_fdset_fd, &mon_fdset->fds, next, mon_fdset_fd_next) {
>> -        if (mon_fdset_fd->removed ||
>> -                (QLIST_EMPTY(&mon_fdset->dup_fds) && mon_refcount == 0)) {
>> +        if ((mon_fdset_fd->removed ||
>> +                (QLIST_EMPTY(&mon_fdset->dup_fds) && mon_refcount == 0)) &&
>> +                runstate_is_running()) {
>
> This condition looks sufficient for command line parsing; however, I
> have to wonder if there are any long-term ill effects, such as if I
> pause a guest, then close an fdset, where qemu keeps the fd open until I
> continue the guest.  But thinking a bit more, we never promised that
> qemu would close fds right away, but only that it wouldn't leak fds by
> closing them whenever qemu thinks it is convenient.
>

I can't think of any ill effects.  I think you may be able to remove an 
fd or fd set followed by adding a drive using that fd set, but that is 
just a difference in behavior compared to when a guest is running.

>>               close(mon_fdset_fd->fd);
>>               g_free(mon_fdset_fd->opaque);
>>               QLIST_REMOVE(mon_fdset_fd, next);
>>
>

-- 
Regards,
Corey Bryant

      reply	other threads:[~2012-10-18 13:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-16 18:08 [Qemu-devel] [PATCH v3 3/4] monitor: Prevent removing fd from set during init Corey Bryant
2012-10-17  4:02 ` Eric Blake
2012-10-18 13:45   ` Corey Bryant [this message]

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=5080080F.2040903@linux.vnet.ibm.com \
    --to=coreyb@linux.vnet.ibm.com \
    --cc=eblake@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=libvir-list@redhat.com \
    --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).