From: Luiz Capitulino <lcapitulino@redhat.com>
To: mdroth@linux.vnet.ibm.com
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 0/2]: qemu-ga: Fix fd handling in daemon mode
Date: Thu, 10 May 2012 16:50:40 -0300 [thread overview]
Message-ID: <1336679442-19198-1-git-send-email-lcapitulino@redhat.com> (raw)
Hi Michael,
There's a problem on how we handle fds in daemon mode that may cause
suspend to fail. This series fixes it. Please, check patch 2/2 for full
details.
qemu-ga.c | 23 ++++++++++++++++++++---
qga/commands-posix.c | 19 -------------------
qga/guest-agent-core.h | 4 ++++
3 files changed, 24 insertions(+), 22 deletions(-)
next reply other threads:[~2012-05-10 19:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 19:50 Luiz Capitulino [this message]
2012-05-10 19:50 ` [Qemu-devel] [PATCH 1/2] qemu-ga: make reopen_fd_to_null() public Luiz Capitulino
2012-05-10 20:14 ` Eric Blake
2012-05-10 19:50 ` [Qemu-devel] [PATCH 2/2] qemu-ga: become_daemon(): reopen standard fds to /dev/null Luiz Capitulino
2012-05-10 20:11 ` Eric Blake
2012-05-11 22:02 ` [Qemu-devel] [PATCH 0/2]: qemu-ga: Fix fd handling in daemon mode Michael Roth
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=1336679442-19198-1-git-send-email-lcapitulino@redhat.com \
--to=lcapitulino@redhat.com \
--cc=mdroth@linux.vnet.ibm.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).