public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mlichvar at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/29417] New: poll() declared with write-only fds Date: Wed, 27 Jul 2022 12:46:01 +0000 [thread overview] Message-ID: <bug-29417-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29417 Bug ID: 29417 Summary: poll() declared with write-only fds Product: glibc Version: 2.36 Status: NEW Severity: normal Priority: P2 Component: libc Assignee: unassigned at sourceware dot org Reporter: mlichvar at redhat dot com CC: drepper.fsp at gmail dot com Target Milestone: --- The poll() function is currently declared as extern int poll (struct pollfd *__fds, nfds_t __nfds, int __timeout) __fortified_attr_access (__write_only__, 1, 2); Is the write-only access of __fds correct? I think the poll function needs to read the fd and events field of pollfd. Maybe I don't understand correctly how it's supposed to work, but the access specified for some other functions made sense to me. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-07-27 12:46 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-27 12:46 mlichvar at redhat dot com [this message] 2022-07-27 15:03 ` [Bug libc/29417] " fweimer at redhat dot com 2022-07-27 15:18 ` mlichvar at redhat dot com 2022-07-27 15:39 ` fweimer at redhat dot com 2022-07-27 18:40 ` siddhesh at sourceware dot org 2022-07-27 18:44 ` siddhesh at sourceware dot org 2022-07-27 18:56 ` fweimer at redhat dot com
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=bug-29417-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@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).