From: Kevin Wolf <kwolf@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org,
Stefan Hajnoczi <stefanha@redhat.com>,
Sascha Silbe <silbe@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH v3 1/3] qemu-nbd: Add --fork option
Date: Tue, 27 Sep 2016 11:04:38 +0200 [thread overview]
Message-ID: <20160927090438.GG4090@noname.str.redhat.com> (raw)
In-Reply-To: <1472142645-7370-2-git-send-email-mreitz@redhat.com>
Am 25.08.2016 um 18:30 hat Max Reitz geschrieben:
> Using the --fork option, one can make qemu-nbd fork the worker process.
> The original process will exit on error of the worker or once the worker
> enters the main loop.
>
> Suggested-by: Sascha Silbe <silbe@linux.vnet.ibm.com>
> Signed-off-by: Max Reitz <mreitz@redhat.com>
> ---
> qemu-nbd.c | 15 ++++++++++++++-
> 1 file changed, 14 insertions(+), 1 deletion(-)
>
> diff --git a/qemu-nbd.c b/qemu-nbd.c
> index e3571c2..8c2d582 100644
> --- a/qemu-nbd.c
> +++ b/qemu-nbd.c
> @@ -48,6 +48,7 @@
> #define QEMU_NBD_OPT_OBJECT 260
> #define QEMU_NBD_OPT_TLSCREDS 261
> #define QEMU_NBD_OPT_IMAGE_OPTS 262
> +#define QEMU_NBD_OPT_FORK 263
>
> #define MBR_SIZE 512
>
> @@ -503,6 +504,7 @@ int main(int argc, char **argv)
> { "tls-creds", required_argument, NULL, QEMU_NBD_OPT_TLSCREDS },
> { "image-opts", no_argument, NULL, QEMU_NBD_OPT_IMAGE_OPTS },
> { "trace", required_argument, NULL, 'T' },
> + { "fork", no_argument, NULL, QEMU_NBD_OPT_FORK },
> { NULL, 0, NULL, 0 }
> };
> int ch;
> @@ -524,6 +526,8 @@ int main(int argc, char **argv)
> bool imageOpts = false;
> bool writethrough = true;
> char *trace_file = NULL;
> + bool fork_process = false;
> + int old_stderr = -1;
>
> /* The client thread uses SIGTERM to interrupt the server. A signal
> * handler ensures that "qemu-nbd -v -c" exits with a nice status code.
> @@ -714,6 +718,9 @@ int main(int argc, char **argv)
> g_free(trace_file);
> trace_file = trace_opt_parse(optarg);
> break;
> + case QEMU_NBD_OPT_FORK:
> + fork_process = true;
> + break;
> }
> }
>
> @@ -773,7 +780,7 @@ int main(int argc, char **argv)
> return 0;
> }
>
> - if (device && !verbose) {
> + if ((device && !verbose) || fork_process) {
> int stderr_fd[2];
> pid_t pid;
> int ret;
> @@ -796,6 +803,7 @@ int main(int argc, char **argv)
> ret = qemu_daemon(1, 0);
>
> /* Temporarily redirect stderr to the parent's pipe... */
> + old_stderr = dup(STDERR_FILENO);
> dup2(stderr_fd[1], STDERR_FILENO);
> if (ret < 0) {
> error_report("Failed to daemonize: %s", strerror(errno));
I don't have a kernel with NBD support, so I can't test this easily, but
doesn't this break the daemon mode for --connect? I mean, it will still
fork, but won't the parent be alive until the child exits?
> @@ -951,6 +959,11 @@ int main(int argc, char **argv)
> exit(EXIT_FAILURE);
> }
>
> + if (fork_process) {
> + dup2(old_stderr, STDERR_FILENO);
> + close(old_stderr);
> + }
Because this code doesn't run for --connect (unless --fork is given,
too).
> state = RUNNING;
> do {
> main_loop_wait(false);
The documentation needs an update, too.
Kevin
next prev parent reply other threads:[~2016-09-27 9:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 16:30 [Qemu-devel] [PATCH v3 0/3] iotests: Fix test 162 Max Reitz
2016-08-25 16:30 ` [Qemu-devel] [PATCH v3 1/3] qemu-nbd: Add --fork option Max Reitz
2016-08-29 16:59 ` Sascha Silbe
2016-09-23 15:16 ` Max Reitz
2016-09-27 9:04 ` Kevin Wolf [this message]
2016-09-27 19:41 ` Max Reitz
2016-08-25 16:30 ` [Qemu-devel] [PATCH v3 2/3] iotests: Remove raciness from 162 Max Reitz
2016-08-25 16:30 ` [Qemu-devel] [PATCH v3 3/3] iotests: Do not rely on unavailable domains in 162 Max Reitz
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=20160927090438.GG4090@noname.str.redhat.com \
--to=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=silbe@linux.vnet.ibm.com \
--cc=stefanha@redhat.com \
/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).