From: Zhi Yong Wu <zwu.kernel@gmail.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: pbonzini@redhat.com, Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>,
qemu-devel@nongnu.org, stefanha@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH v5 2/2] net: add the support for -netdev socket, listen
Date: Sat, 9 Jun 2012 10:09:44 +0800 [thread overview]
Message-ID: <CAEH94LjFZFEXXBpWYmhczx0SP4LZU97DiuwazhoV-i4w2skawQ@mail.gmail.com> (raw)
In-Reply-To: <CAJSP0QUJY58ju1q-yO=qeSMtBoocpedqypGGQpLBrvP51BTNdA@mail.gmail.com>
On Fri, Jun 8, 2012 at 11:59 PM, Stefan Hajnoczi <stefanha@gmail.com> wrote:
> On Fri, Jun 8, 2012 at 3:54 PM, Zhi Yong Wu <zwu.kernel@gmail.com> wrote:
>> On Fri, Jun 8, 2012 at 6:31 PM, Stefan Hajnoczi <stefanha@gmail.com> wrote:
>>> On Thu, Jun 7, 2012 at 3:54 PM, <zwu.kernel@gmail.com> wrote:
>>>> @@ -86,7 +82,16 @@ static void net_socket_send(void *opaque)
>>>> /* end of connection */
>>>> eoc:
>>>> qemu_set_fd_handler(s->fd, NULL, NULL, NULL);
>>>> + qemu_set_fd_handler(s->listen_fd, net_socket_accept, NULL, s);
>>>
>>> What happens when this is not a listen socket? I suggest setting
>>> listen_fd to -1 during creation and not calling qemu_set_fd_handler()
>>> when listen_fd is -1 here. If listen_fd is 0 then we'll register
>>> net_socket_accept when standard input becomes ready!
>>>
>>>> closesocket(s->fd);
>>>> +
>>>> + s->fd = 0;
>>>
>>> -1 should be used since 0 is a valid file descriptor (standard input).
>> I think that s->fd = 0 doesn't cause every issue. When it is zero,
>> this fd hasn't been registered with every handler. You can see that
>> "qemu_set_fd_handler(s->fd, NULL, NULL, NULL);" before "s->fd = 0".
>
> If s->fd = 0 because we are still listening and net_socket_cleanup()
OK, done. any other issue?
> is called we will close() standard input.
>
> Stefan
--
Regards,
Zhi Yong Wu
next prev parent reply other threads:[~2012-06-09 2:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-07 14:54 [Qemu-devel] [PATCH v5 2/2] net: add the support for -netdev socket, listen zwu.kernel
2012-06-08 10:31 ` Stefan Hajnoczi
2012-06-08 14:15 ` Zhi Yong Wu
2012-06-08 14:20 ` Stefan Hajnoczi
2012-06-08 14:34 ` Zhi Yong Wu
2012-06-08 14:46 ` Zhi Yong Wu
2012-06-08 14:54 ` Zhi Yong Wu
2012-06-08 15:59 ` Stefan Hajnoczi
2012-06-09 2:09 ` Zhi Yong Wu [this message]
2012-06-11 9:01 ` Stefan Hajnoczi
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=CAEH94LjFZFEXXBpWYmhczx0SP4LZU97DiuwazhoV-i4w2skawQ@mail.gmail.com \
--to=zwu.kernel@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=stefanha@linux.vnet.ibm.com \
--cc=wuzhy@linux.vnet.ibm.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).