public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc] Add access function attributes to epoll_wait Date: Mon, 14 Mar 2022 15:19:58 +0000 (GMT) [thread overview] Message-ID: <20220314151958.85C553857034@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=0c03669626f1a24e66ce0e350fd020533b0b926d commit 0c03669626f1a24e66ce0e350fd020533b0b926d Author: Steve Grubb <sgrubb@redhat.com> Date: Fri Mar 11 09:40:41 2022 -0500 Add access function attributes to epoll_wait This patch adds write access function attributes to the epoll_wait family of functions Reviewed-by: Siddhesh Poyarekar <siddhesh@sourceware.org> Diff: --- sysdeps/unix/sysv/linux/sys/epoll.h | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/sysdeps/unix/sysv/linux/sys/epoll.h b/sysdeps/unix/sysv/linux/sys/epoll.h index b95ca68749..aa90441e91 100644 --- a/sysdeps/unix/sysv/linux/sys/epoll.h +++ b/sysdeps/unix/sysv/linux/sys/epoll.h @@ -122,7 +122,8 @@ extern int epoll_ctl (int __epfd, int __op, int __fd, This function is a cancellation point and therefore not marked with __THROW. */ extern int epoll_wait (int __epfd, struct epoll_event *__events, - int __maxevents, int __timeout); + int __maxevents, int __timeout) + __attr_access ((__write_only__, 2, 3)); /* Same as epoll_wait, but the thread's signal mask is temporarily @@ -132,7 +133,8 @@ extern int epoll_wait (int __epfd, struct epoll_event *__events, __THROW. */ extern int epoll_pwait (int __epfd, struct epoll_event *__events, int __maxevents, int __timeout, - const __sigset_t *__ss); + const __sigset_t *__ss) + __attr_access ((__write_only__, 2, 3)); /* Same as epoll_pwait, but the timeout as a timespec. @@ -141,14 +143,16 @@ extern int epoll_pwait (int __epfd, struct epoll_event *__events, #ifndef __USE_TIME_BITS64 extern int epoll_pwait2 (int __epfd, struct epoll_event *__events, int __maxevents, const struct timespec *__timeout, - const __sigset_t *__ss); + const __sigset_t *__ss) + __attr_access ((__write_only__, 2, 3)); #else # ifdef __REDIRECT extern int __REDIRECT (epoll_pwait2, (int __epfd, struct epoll_event *__ev, int __maxevs, const struct timespec *__timeout, const __sigset_t *__ss), - __epoll_pwait2_time64); + __epoll_pwait2_time64) + __attr_access ((__write_only__, 2, 3)); # else # define epoll_pwait2 __epoll_pwait2_time64 # endif
reply other threads:[~2022-03-14 15:19 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220314151958.85C553857034@sourceware.org \ --to=siddhesh@sourceware.org \ --cc=glibc-cvs@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: linkBe 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).