From: Anthony Liguori <aliguori@us.ibm.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qemu-char: use qemu_set_fd_handler/2 consistently
Date: Fri, 23 Sep 2011 13:50:49 -0500 [thread overview]
Message-ID: <4E7CD509.4020009@us.ibm.com> (raw)
In-Reply-To: <20110916211955.GA13940@amt.cnet>
On 09/16/2011 04:19 PM, Marcelo Tosatti wrote:
>
> Now that qemu_set_fd_handler and qemu_set_fd_handler2 have different
> implementations, one using qemu iohandlers and the other glib, it is not
> safe to mix the two when inserting/deleting handlers.
>
> Fixes kvm-autotest.
>
> Signed-off-by: Marcelo Tosatti<mtosatti@redhat.com>
Applied. Thanks.
Regards,
Anthony Liguori
>
> diff --git a/qemu-char.c b/qemu-char.c
> index c9e5c41..09d2309 100644
> --- a/qemu-char.c
> +++ b/qemu-char.c
> @@ -1881,7 +1881,7 @@ static void udp_chr_close(CharDriverState *chr)
> {
> NetCharDriver *s = chr->opaque;
> if (s->fd>= 0) {
> - qemu_set_fd_handler(s->fd, NULL, NULL, NULL);
> + qemu_set_fd_handler2(s->fd, NULL, NULL, NULL, NULL);
> closesocket(s->fd);
> }
> g_free(s);
> @@ -2093,9 +2093,9 @@ static void tcp_chr_read(void *opaque)
> /* connection closed */
> s->connected = 0;
> if (s->listen_fd>= 0) {
> - qemu_set_fd_handler(s->listen_fd, tcp_chr_accept, NULL, chr);
> + qemu_set_fd_handler2(s->listen_fd, NULL, tcp_chr_accept, NULL, chr);
> }
> - qemu_set_fd_handler(s->fd, NULL, NULL, NULL);
> + qemu_set_fd_handler2(s->fd, NULL, NULL, NULL, NULL);
> closesocket(s->fd);
> s->fd = -1;
> qemu_chr_event(chr, CHR_EVENT_CLOSED);
> @@ -2156,7 +2156,7 @@ static int tcp_chr_add_client(CharDriverState *chr, int fd)
> if (s->do_nodelay)
> socket_set_nodelay(fd);
> s->fd = fd;
> - qemu_set_fd_handler(s->listen_fd, NULL, NULL, NULL);
> + qemu_set_fd_handler2(s->listen_fd, NULL, NULL, NULL, NULL);
> tcp_chr_connect(chr);
>
> return 0;
> @@ -2202,11 +2202,11 @@ static void tcp_chr_close(CharDriverState *chr)
> {
> TCPCharDriver *s = chr->opaque;
> if (s->fd>= 0) {
> - qemu_set_fd_handler(s->fd, NULL, NULL, NULL);
> + qemu_set_fd_handler2(s->fd, NULL, NULL, NULL, NULL);
> closesocket(s->fd);
> }
> if (s->listen_fd>= 0) {
> - qemu_set_fd_handler(s->listen_fd, NULL, NULL, NULL);
> + qemu_set_fd_handler2(s->listen_fd, NULL, NULL, NULL, NULL);
> closesocket(s->listen_fd);
> }
> g_free(s);
> @@ -2272,7 +2272,7 @@ static int qemu_chr_open_socket(QemuOpts *opts, CharDriverState **_chr)
>
> if (is_listen) {
> s->listen_fd = fd;
> - qemu_set_fd_handler(s->listen_fd, tcp_chr_accept, NULL, chr);
> + qemu_set_fd_handler2(s->listen_fd, NULL, tcp_chr_accept, NULL, chr);
> if (is_telnet)
> s->do_telnetopt = 1;
>
>
>
prev parent reply other threads:[~2011-09-23 18:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-16 21:19 [Qemu-devel] [PATCH] qemu-char: use qemu_set_fd_handler/2 consistently Marcelo Tosatti
2011-09-23 18:50 ` Anthony Liguori [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=4E7CD509.4020009@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=mtosatti@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 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.