From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
Anthony Liguori <aliguori@amazon.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: [Qemu-devel] [PATCH for-2.1 0/2] qemu-char: fixes to the new get_msgfds API
Date: Sun, 22 Jun 2014 10:38:35 +0800 [thread overview]
Message-ID: <1403404717-12101-1-git-send-email-stefanha@redhat.com> (raw)
The recent changes to extend qemu-char get_msgfds to support multiple file
descriptors caused a qemu-iotests regression and also introduced a file
descriptor leak. This patch series fixes the bugs.
Stefan Hajnoczi (2):
qemu-char: fix qemu_chr_fe_get_msgfd()
qemu-char: avoid leaking unused fds in tcp_get_msgfds()
qemu-char.c | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
--
1.9.3
next reply other threads:[~2014-06-22 2:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-22 2:38 Stefan Hajnoczi [this message]
2014-06-22 2:38 ` [Qemu-devel] [PATCH for-2.1 1/2] qemu-char: fix qemu_chr_fe_get_msgfd() Stefan Hajnoczi
2014-06-22 2:38 ` [Qemu-devel] [PATCH for-2.1 2/2] qemu-char: avoid leaking unused fds in tcp_get_msgfds() Stefan Hajnoczi
2014-06-22 10:53 ` [Qemu-devel] [PATCH for-2.1 0/2] qemu-char: fixes to the new get_msgfds API Michael S. Tsirkin
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=1403404717-12101-1-git-send-email-stefanha@redhat.com \
--to=stefanha@redhat.com \
--cc=aliguori@amazon.com \
--cc=mst@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).