From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: Eric Blake <eblake@redhat.com>, qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v2] qemu-ga: guest-shutdown: use only async-signal-safe functions
Date: Mon, 14 May 2012 17:25:04 -0500 [thread overview]
Message-ID: <20120514222504.GG28865@illuin> (raw)
In-Reply-To: <20120514152520.69ce699a@doriath.home>
On Mon, May 14, 2012 at 03:25:20PM -0300, Luiz Capitulino wrote:
> POSIX mandates[1] that a child process of a multi-thread program uses
> only async-signal-safe functions before exec(). We consider qemu-ga
> to be multi-thread, because it uses glib.
>
> However, qmp_guest_shutdown() uses functions that are not
> async-signal-safe. Fix it the following way:
>
> - fclose() -> reopen_fd_to_null()
> - execl() -> execle()
> - exit() -> _exit()
> - drop slog() usage (which is not safe)
>
> [1] http://pubs.opengroup.org/onlinepubs/009695399/functions/fork.html
>
> Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
Thanks, applied to qga branch.
> ---
>
> o v2
>
> - fix doc typo
> - drop 'ret' and use EXIT_FAILURE instead
>
> qapi-schema-guest.json | 3 +--
> qga/commands-posix.c | 19 ++++++++-----------
> 2 files changed, 9 insertions(+), 13 deletions(-)
>
> diff --git a/qapi-schema-guest.json b/qapi-schema-guest.json
> index 1c949ff..bd2256d 100644
> --- a/qapi-schema-guest.json
> +++ b/qapi-schema-guest.json
> @@ -126,8 +126,7 @@
> # @guest-shutdown:
> #
> # Initiate guest-activated shutdown. Note: this is an asynchronous
> -# shutdown request, with no guaruntee of successful shutdown. Errors
> -# will be logged to guest's syslog.
> +# shutdown request, with no guarantee of successful shutdown.
> #
> # @mode: #optional "halt", "powerdown" (default), or "reboot"
> #
> diff --git a/qga/commands-posix.c b/qga/commands-posix.c
> index 9a59276..15ce928 100644
> --- a/qga/commands-posix.c
> +++ b/qga/commands-posix.c
> @@ -37,8 +37,8 @@
> void qmp_guest_shutdown(bool has_mode, const char *mode, Error **err)
> {
> const char *shutdown_flag;
> - int ret, status;
> pid_t rpid, pid;
> + int status;
>
> slog("guest-shutdown called, mode: %s", mode);
> if (!has_mode || strcmp(mode, "powerdown") == 0) {
> @@ -57,16 +57,13 @@ void qmp_guest_shutdown(bool has_mode, const char *mode, Error **err)
> if (pid == 0) {
> /* child, start the shutdown */
> setsid();
> - fclose(stdin);
> - fclose(stdout);
> - fclose(stderr);
> -
> - ret = execl("/sbin/shutdown", "shutdown", shutdown_flag, "+0",
> - "hypervisor initiated shutdown", (char*)NULL);
> - if (ret) {
> - slog("guest-shutdown failed: %s", strerror(errno));
> - }
> - exit(!!ret);
> + reopen_fd_to_null(0);
> + reopen_fd_to_null(1);
> + reopen_fd_to_null(2);
> +
> + execle("/sbin/shutdown", "shutdown", shutdown_flag, "+0",
> + "hypervisor initiated shutdown", (char*)NULL, environ);
> + _exit(EXIT_FAILURE);
> } else if (pid < 0) {
> goto exit_err;
> }
> --
> 1.7.9.2.384.g4a92a
>
prev parent reply other threads:[~2012-05-14 22:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 18:25 [Qemu-devel] [PATCH v2] qemu-ga: guest-shutdown: use only async-signal-safe functions Luiz Capitulino
2012-05-14 20:00 ` Eric Blake
2012-05-14 22:25 ` Michael Roth [this message]
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=20120514222504.GG28865@illuin \
--to=mdroth@linux.vnet.ibm.com \
--cc=eblake@redhat.com \
--cc=lcapitulino@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).