From: Peter Maydell <peter.maydell@linaro.org>
To: qemu-devel@nongnu.org
Cc: Laurent Vivier <laurent@vivier.eu>
Subject: Re: [PATCH] linux-user: Remove pointless NULL check in clock_adjtime handling
Date: Tue, 4 Jul 2023 14:26:51 +0100 [thread overview]
Message-ID: <CAFEAcA_mezDNCR0JwsURzZ1gSeAk64H81CVOzWPyur94uEFfKg@mail.gmail.com> (raw)
In-Reply-To: <20230623144410.1837261-1-peter.maydell@linaro.org>
Laurent, ping? This patch has been reviewed.
thanks
-- PMM
On Fri, 23 Jun 2023 at 15:44, Peter Maydell <peter.maydell@linaro.org> wrote:
>
> In the code for TARGET_NR_clock_adjtime, we set the pointer phtx to
> the address of the local variable htx. This means it can never be
> NULL, but later in the code we check it for NULL anyway. Coverity
> complains about this (CID 1507683) because the NULL check comes after
> a call to clock_adjtime() that assumes it is non-NULL.
>
> Since phtx is always &htx, and is used only in three places, it's not
> really necessary. Remove it, bringing the code structure in to line
> with that for TARGET_NR_clock_adjtime64, which already uses a simple
> '&htx' when it wants a pointer to 'htx'.
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> linux-user/syscall.c | 12 +++++-------
> 1 file changed, 5 insertions(+), 7 deletions(-)
>
> diff --git a/linux-user/syscall.c b/linux-user/syscall.c
> index f2cb101d83c..7b2f9f7340e 100644
> --- a/linux-user/syscall.c
> +++ b/linux-user/syscall.c
> @@ -10935,16 +10935,14 @@ static abi_long do_syscall1(CPUArchState *cpu_env, int num, abi_long arg1,
> #if defined(TARGET_NR_clock_adjtime) && defined(CONFIG_CLOCK_ADJTIME)
> case TARGET_NR_clock_adjtime:
> {
> - struct timex htx, *phtx = &htx;
> + struct timex htx;
>
> - if (target_to_host_timex(phtx, arg2) != 0) {
> + if (target_to_host_timex(&htx, arg2) != 0) {
> return -TARGET_EFAULT;
> }
> - ret = get_errno(clock_adjtime(arg1, phtx));
> - if (!is_error(ret) && phtx) {
> - if (host_to_target_timex(arg2, phtx) != 0) {
> - return -TARGET_EFAULT;
> - }
> + ret = get_errno(clock_adjtime(arg1, &htx));
> + if (!is_error(ret) && host_to_target_timex(arg2, &htx)) {
> + return -TARGET_EFAULT;
> }
> }
> return ret;
> --
next prev parent reply other threads:[~2023-07-04 13:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 14:44 [PATCH] linux-user: Remove pointless NULL check in clock_adjtime handling Peter Maydell
2023-06-23 15:18 ` Philippe Mathieu-Daudé
2023-06-26 8:27 ` Richard Henderson
2023-07-04 13:26 ` Peter Maydell [this message]
2023-07-13 13:10 ` 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=CAFEAcA_mezDNCR0JwsURzZ1gSeAk64H81CVOzWPyur94uEFfKg@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=laurent@vivier.eu \
--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).