From: Anthony Liguori <aliguori@us.ibm.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2] qemu-char: BUGFIX, don't call FD_ISSET with negative fd
Date: Mon, 17 Sep 2012 13:24:51 -0500 [thread overview]
Message-ID: <87txuw4ido.fsf@codemonkey.ws> (raw)
In-Reply-To: <1347244257-15586-2-git-send-email-david@gibson.dropbear.id.au>
David Gibson <david@gibson.dropbear.id.au> writes:
> tcp_chr_connect(), unlike for example udp_chr_update_read_handler() does
> not check if the fd it is using is valid (>= 0) before passing it to
> qemu_set_fd_handler2(). If using e.g. a TCP serial port, which is not
> initially connected, this can result in -1 being passed to FD_ISSET, which
> has undefined behaviour. On x86 it seems to harmlessly return 0, but on
> PowerPC, it causes a fortify buffer overflow error to be thrown.
>
> This patch fixes this by putting an extra test in tcp_chr_connect(), and
> also adds an assert qemu_set_fd_handler2() to catch other such errors on
> all platforms, rather than just some.
>
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Applied. Thanks.
Regards,
Anthony Liguori
> ---
> iohandler.c | 2 ++
> qemu-char.c | 6 ++++--
> 2 files changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/iohandler.c b/iohandler.c
> index dea4355..a2d871b 100644
> --- a/iohandler.c
> +++ b/iohandler.c
> @@ -56,6 +56,8 @@ int qemu_set_fd_handler2(int fd,
> {
> IOHandlerRecord *ioh;
>
> + assert(fd >= 0);
> +
> if (!fd_read && !fd_write) {
> QLIST_FOREACH(ioh, &io_handlers, next) {
> if (ioh->fd == fd) {
> diff --git a/qemu-char.c b/qemu-char.c
> index 398baf1..73e48ff 100644
> --- a/qemu-char.c
> +++ b/qemu-char.c
> @@ -2332,8 +2332,10 @@ static void tcp_chr_connect(void *opaque)
> TCPCharDriver *s = chr->opaque;
>
> s->connected = 1;
> - qemu_set_fd_handler2(s->fd, tcp_chr_read_poll,
> - tcp_chr_read, NULL, chr);
> + if (s->fd >= 0) {
> + qemu_set_fd_handler2(s->fd, tcp_chr_read_poll,
> + tcp_chr_read, NULL, chr);
> + }
> qemu_chr_generic_open(chr);
> }
>
> --
> 1.7.10.4
next prev parent reply other threads:[~2012-09-17 18:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 2:30 [Qemu-devel] [0/2] Bugfixes for 1.2 stable series David Gibson
2012-09-10 2:30 ` [Qemu-devel] [PATCH 1/2] qemu-char: BUGFIX, don't call FD_ISSET with negative fd David Gibson
2012-09-17 18:24 ` Anthony Liguori [this message]
2012-09-18 0:08 ` David Gibson
2012-09-18 11:29 ` Andreas Färber
2012-09-19 0:30 ` David Gibson
2012-09-10 2:30 ` [Qemu-devel] [PATCH 2/2] cpu_physical_memory_write_rom() needs to do TB invalidates David Gibson
2012-09-10 13:27 ` Andreas Färber
2012-09-12 5:57 ` David Gibson
2012-10-01 13:43 ` Pavel Hrdina
2012-10-01 14:28 ` Anthony Liguori
2012-10-01 15:34 ` Pavel Hrdina
2012-10-01 16:21 ` Anthony Liguori
2012-10-01 16:25 ` Pavel Hrdina
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=87txuw4ido.fsf@codemonkey.ws \
--to=aliguori@us.ibm.com \
--cc=david@gibson.dropbear.id.au \
--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.