public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libc/31917] New: clang mq_open fortify wrapper does not handle 4 argument correctly
@ 2024-06-20 13:34 adhemerval.zanella at linaro dot org
2024-06-27 16:35 ` [Bug libc/31917] " adhemerval.zanella at linaro dot org
2024-06-27 16:36 ` adhemerval.zanella at linaro dot org
0 siblings, 2 replies; 3+ messages in thread
From: adhemerval.zanella at linaro dot org @ 2024-06-20 13:34 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=31917
Bug ID: 31917
Summary: clang mq_open fortify wrapper does not handle 4
argument correctly
Product: glibc
Version: 2.39
Status: NEW
Severity: normal
Priority: P2
Component: libc
Assignee: unassigned at sourceware dot org
Reporter: adhemerval.zanella at linaro dot org
CC: drepper.fsp at gmail dot com
Target Milestone: ---
For instance, building socat 1.8 with a yocto clang based system shows:
./socat-1.8.0.0/xio-posixmq.c:119:8: error: 'mq_open' is unavailable:
mq_open can be called either with 2 or 4 arguments
119 | mqd = mq_open(name, oflag, opt_mode, NULL);
| ^
[...] /usr/include/bits/mqueue2.h:66:8: note: 'mq_open' has been
explicitly marked unavailable here
66 | __NTH (mq_open (const char *__name, int __oflag, mode_t mode,
| ^
1 error generated.
Where GCC correctly does not show any warning message.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug libc/31917] clang mq_open fortify wrapper does not handle 4 argument correctly
2024-06-20 13:34 [Bug libc/31917] New: clang mq_open fortify wrapper does not handle 4 argument correctly adhemerval.zanella at linaro dot org
@ 2024-06-27 16:35 ` adhemerval.zanella at linaro dot org
2024-06-27 16:36 ` adhemerval.zanella at linaro dot org
1 sibling, 0 replies; 3+ messages in thread
From: adhemerval.zanella at linaro dot org @ 2024-06-27 16:35 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=31917
Adhemerval Zanella <adhemerval.zanella at linaro dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |2.40
Status|NEW |RESOLVED
Assignee|unassigned at sourceware dot org |adhemerval.zanella at linaro dot o
| |rg
Resolution|--- |FIXED
--- Comment #1 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> ---
Fixed on 2.40.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug libc/31917] clang mq_open fortify wrapper does not handle 4 argument correctly
2024-06-20 13:34 [Bug libc/31917] New: clang mq_open fortify wrapper does not handle 4 argument correctly adhemerval.zanella at linaro dot org
2024-06-27 16:35 ` [Bug libc/31917] " adhemerval.zanella at linaro dot org
@ 2024-06-27 16:36 ` adhemerval.zanella at linaro dot org
1 sibling, 0 replies; 3+ messages in thread
From: adhemerval.zanella at linaro dot org @ 2024-06-27 16:36 UTC (permalink / raw)
To: glibc-bugs
https://sourceware.org/bugzilla/show_bug.cgi?id=31917
Adhemerval Zanella <adhemerval.zanella at linaro dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|2.39 |2.40
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2024-06-27 16:36 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2024-06-20 13:34 [Bug libc/31917] New: clang mq_open fortify wrapper does not handle 4 argument correctly adhemerval.zanella at linaro dot org
2024-06-27 16:35 ` [Bug libc/31917] " adhemerval.zanella at linaro dot org
2024-06-27 16:36 ` adhemerval.zanella at linaro dot org
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).