From: Florian Weimer <fweimer@redhat.com>
To: Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH] posix: Fix -Warray-bounds instances building timer_create [BZ #26687]
Date: Tue, 06 Oct 2020 13:27:42 +0200 [thread overview]
Message-ID: <878scjtx01.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <20201005211234.2240007-1-adhemerval.zanella@linaro.org> (Adhemerval Zanella via Libc-alpha's message of "Mon, 5 Oct 2020 18:12:33 -0300")
* Adhemerval Zanella via Libc-alpha:
> diff --git a/sysdeps/unix/sysv/linux/timer_create.c b/sysdeps/unix/sysv/linux/timer_create.c
> index 370c99a517..69b4e667fa 100644
> --- a/sysdeps/unix/sysv/linux/timer_create.c
> +++ b/sysdeps/unix/sysv/linux/timer_create.c
> @@ -149,27 +122,24 @@ timer_create (clockid_t clock_id, struct sigevent *evp, timer_t *timerid)
>
> /* Create the timer. */
> int res;
> + res = INTERNAL_SYSCALL_CALL (timer_create, syscall_clockid, &sev,
> + &newp->ktimerid);
> + if (res == -1)
> {
> + free (newp);
> + __set_errno (INTERNAL_SYSCALL_ERRNO (res));
> + return -1;
> }
This does not look like a correct use of INTERNAL_SYSCALL_CALL to me.
Don't you have to use INTERNAL_SYSCALL_ERROR_P here?
Thanks,
Florian
--
Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill
next prev parent reply other threads:[~2020-10-06 11:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-05 21:12 Adhemerval Zanella
2020-10-06 8:13 ` Florian Weimer
2020-10-06 8:21 ` Florian Weimer
2020-10-06 14:00 ` Adhemerval Zanella
2020-10-06 14:13 ` Florian Weimer
2020-10-06 14:24 ` Adhemerval Zanella
2020-10-06 11:27 ` Florian Weimer [this message]
2020-10-06 13:57 ` Adhemerval Zanella
2020-10-06 14:14 ` Florian Weimer
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=878scjtx01.fsf@oldenburg2.str.redhat.com \
--to=fweimer@redhat.com \
--cc=libc-alpha@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).