From: Peter Maydell <peter.maydell@linaro.org>
To: Alexander Graf <agraf@suse.de>
Cc: riku.voipio@iki.fi, qemu-devel Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] linux-user: fix wait* syscall status returns
Date: Wed, 23 Nov 2011 21:55:38 +0000 [thread overview]
Message-ID: <CAFEAcA8VDCcjoeFhWiq2AwLn5UJsG93-2xsc+QT2+qDa24kaCg@mail.gmail.com> (raw)
In-Reply-To: <1322080707-13527-1-git-send-email-agraf@suse.de>
On 23 November 2011 20:38, Alexander Graf <agraf@suse.de> wrote:
> When calling wait4 or waitpid with a status pointer and WNOHANG, the
> syscall can potentially not modify the status pointer input. Now if we
> have guest code like:
>
> int status = 0;
> waitpid(pid, &status, WNOHANG);
> if (status)
> <breakage>
>
> then we have to make sure that in case status did not change we actually
> return the guest's initialized status variable instead of our own uninitialized.
> We fail to do so today, as we proxy everything through an uninitialized status
> variable which for me ended up always containing the last error code.
>
> This patch fixes some test cases when building yast2-core in OBS for ARM.
>
> Signed-off-by: Alexander Graf <agraf@suse.de>
> ---
> linux-user/syscall.c | 8 +++++++-
> 1 files changed, 7 insertions(+), 1 deletions(-)
>
> diff --git a/linux-user/syscall.c b/linux-user/syscall.c
> index 3e6f3bd..f86fe4a 100644
> --- a/linux-user/syscall.c
> +++ b/linux-user/syscall.c
> @@ -4833,7 +4833,10 @@ abi_long do_syscall(void *cpu_env, int num, abi_long arg1,
> #ifdef TARGET_NR_waitpid
> case TARGET_NR_waitpid:
> {
> - int status;
> + int status = 0;
> + if (arg2) {
> + get_user_s32(status, arg2);
> + }
> ret = get_errno(waitpid(arg1, &status, arg3));
> if (!is_error(ret) && arg2
> && put_user_s32(host_to_target_waitstatus(status), arg2))
If the problem is that waitpid() can return success without writing to
status, then this code is still not right because we will get the
initial target waitstatus into status, and then pass it through
host_to_target_waitstatus(), possibly modifying it, before writing
it back to guest memory.
I think waitpid() will always and only write to status if the return
value is > 0 (ie it's a PID, not 0 or -1). So I think the right fix
for this problem is to have the if() protecting the put_user_s32()
read "if (ret && !is_error(ret) && ...".
(ret == 0 is of course the WNOHANG-and-no-child-yet case you are hitting.)
> @@ -6389,6 +6392,9 @@ abi_long do_syscall(void *cpu_env, int num, abi_long arg1,
> rusage_ptr = &rusage;
> else
> rusage_ptr = NULL;
> + if (status_ptr) {
> + get_user_s32(status, status_ptr);
> + }
> ret = get_errno(wait4(arg1, &status, arg3, rusage_ptr));
> if (!is_error(ret)) {
> if (status_ptr) {
...and similarly here.
-- PMM
next prev parent reply other threads:[~2011-11-23 21:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 20:38 [Qemu-devel] [PATCH] linux-user: fix wait* syscall status returns Alexander Graf
2011-11-23 21:55 ` Peter Maydell [this message]
2011-11-23 22:03 ` Alexander Graf
2011-11-23 22:34 ` Peter Maydell
2011-11-23 23:00 ` Alexander Graf
2011-11-23 23:02 ` Peter Maydell
2011-11-23 23:31 ` Alexander Graf
2011-11-23 23:48 ` Peter Maydell
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=CAFEAcA8VDCcjoeFhWiq2AwLn5UJsG93-2xsc+QT2+qDa24kaCg@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=agraf@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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).