public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mliska at suse dot cz" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug stdio/27024] New: Wrong access (read_only, 3, 4) attribute for readlinkat
Date: Sun, 06 Dec 2020 14:45:41 +0000 [thread overview]
Message-ID: <bug-27024-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27024
Bug ID: 27024
Summary: Wrong access (read_only, 3, 4) attribute for
readlinkat
Product: glibc
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: stdio
Assignee: unassigned at sourceware dot org
Reporter: mliska at suse dot cz
CC: msebor at redhat dot com
Target Milestone: ---
Since g:06febd8c670, there's a bad access attribute:
posix/unistd.h:
/* Like readlink but a relative PATH is interpreted relative to FD. */
extern ssize_t readlinkat (int __fd, const char *__restrict __path,
char *__restrict __buf, size_t __len)
__THROW __nonnull ((2, 3)) __wur __attr_access ((__read_only__, 3, 4));
#endif
it guess it should be write_only.
@Martin: Can you please take a look?
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2020-12-06 14:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-06 14:45 mliska at suse dot cz [this message]
2021-01-06 3:53 ` [Bug stdio/27024] " richardpku at gmail dot com
2021-01-06 5:21 ` mliska at suse dot cz
2021-01-06 15:53 ` msebor at gmail dot com
2021-01-06 16:07 ` mliska at suse dot cz
2021-01-08 0:49 ` msebor at gmail dot com
2021-01-10 20:52 ` msebor at redhat dot com
2021-02-07 15:24 ` 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-27024-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: 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).