qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 0/4] fix qemu-nbd -c
Date: Fri, 28 Oct 2011 12:17:53 +0200	[thread overview]
Message-ID: <1319797077-25441-1-git-send-email-pbonzini@redhat.com> (raw)

qemu-nbd -c is another casualty of removing raw_read/raw_write.  This
series fixes it.

Unfortunately, as a side effect of this qemu-nbd will have to daemonize
before detecting all possible errors.  For this reason patches 2 and 3
make qemu-nbd write errors to syslog when daemonized.

Paolo Bonzini (4):
  qemu-nbd: exit if the child exits before a socket connection is
    established
  qemu-nbd: include our own err/errx implementation
  qemu-nbd: report errors to syslog when daemonized
  qemu-nbd: do not start the block layer in the parent

 qemu-nbd.c |   78 +++++++++++++++++++++++++++++++++++++++++++++--------------
 1 files changed, 59 insertions(+), 19 deletions(-)

-- 
1.7.6.4

             reply	other threads:[~2011-10-28 10:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-28 10:17 Paolo Bonzini [this message]
2011-10-28 10:17 ` [Qemu-devel] [PATCH 1/4] qemu-nbd: exit if the child exits before a socket connection is established Paolo Bonzini
2011-10-28 10:17 ` [Qemu-devel] [PATCH 2/4] qemu-nbd: include our own err/errx implementation Paolo Bonzini
2011-10-28 10:17 ` [Qemu-devel] [PATCH 3/4] qemu-nbd: report errors to syslog when daemonized Paolo Bonzini
2011-10-28 10:17 ` [Qemu-devel] [PATCH 4/4] qemu-nbd: do not start the block layer in the parent Paolo Bonzini
2011-10-28 11:56   ` Pierre Riteau
2011-10-28 11:57     ` Paolo Bonzini
2011-10-28 12:16       ` Pierre Riteau
2011-10-28 12:17         ` Paolo Bonzini
2011-11-04  9:46           ` Paolo Bonzini
2011-11-04 10:31             ` Kevin Wolf
2011-11-04 11:10               ` Paolo Bonzini
2011-11-04 11:22                 ` Kevin Wolf
2011-11-04 11:25                   ` Paolo Bonzini

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=1319797077-25441-1-git-send-email-pbonzini@redhat.com \
    --to=pbonzini@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).