From: Laurent Vivier <laurent@vivier.eu>
To: Max Filippov <jcmvbkbc@gmail.com>, qemu-devel@nongnu.org
Cc: Riku Voipio <riku.voipio@iki.fi>
Subject: Re: [Qemu-devel] [PATCH] linux-user: fix error propagation in clock_gettime
Date: Sun, 1 Apr 2018 23:05:04 +0200 [thread overview]
Message-ID: <26d50d9e-20a4-08e5-a860-e0cae22efd29@vivier.eu> (raw)
In-Reply-To: <20180401203739.31670-1-jcmvbkbc@gmail.com>
Le 01/04/2018 à 22:37, Max Filippov a écrit :
> host_to_target_timespec may return error if target address could not be
> locked, but it is ignored.
> Propagate return value of host_to_target_timespec to the caller of
> clock_gettime.
>
> Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
> ---
> linux-user/syscall.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/linux-user/syscall.c b/linux-user/syscall.c
> index d51e2a00ee31..52e2f9c16479 100644
> --- a/linux-user/syscall.c
> +++ b/linux-user/syscall.c
> @@ -11884,7 +11884,7 @@ abi_long do_syscall(void *cpu_env, int num, abi_long arg1,
> struct timespec ts;
> ret = get_errno(clock_gettime(arg1, &ts));
> if (!is_error(ret)) {
> - host_to_target_timespec(arg2, &ts);
> + ret = host_to_target_timespec(arg2, &ts);
> }
> break;
> }
>
Could you also update in the same way clock_getres?
There are other syscalls ignoring result of host_to_target_timespec(),
but they are also ignoring result of target_to_host_timespec, but I
don't think the -rc stage is the good moment to fix them all.
Thanks,
Laurent
next prev parent reply other threads:[~2018-04-01 21:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-01 20:37 [Qemu-devel] [PATCH] linux-user: fix error propagation in clock_gettime Max Filippov
2018-04-01 20:48 ` no-reply
2018-04-01 21:05 ` Laurent Vivier [this message]
2018-04-01 21:15 ` Laurent Vivier
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=26d50d9e-20a4-08e5-a860-e0cae22efd29@vivier.eu \
--to=laurent@vivier.eu \
--cc=jcmvbkbc@gmail.com \
--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).