public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug network/28846] New: CMSG_NXTHDR may trigger -Wstrict-overflow warning Date: Tue, 01 Feb 2022 14:55:19 +0000 [thread overview] Message-ID: <bug-28846-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=28846 Bug ID: 28846 Summary: CMSG_NXTHDR may trigger -Wstrict-overflow warning Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: network Assignee: unassigned at sourceware dot org Reporter: fweimer at redhat dot com Target Milestone: --- Flags: security- Downstream bug report from Andreas Schneider: “ This is actually a bug in /usr/include/bits/socket.h with -Werror=strict-overflow. The compiler complains about the CMSG_NXTHDR() macro. In file included from /usr/include/sys/socket.h:33, from /builddir/build/BUILD/socket_wrapper-1.3.3/src/socket_wrapper.c:50: In function '__cmsg_nxthdr', inlined from 'test_sendmsg_cmsg' at /builddir/build/BUILD/socket_wrapper-1.3.3/tests/test_swrap_unit.c:73:9: /usr/include/bits/socket.h:322:6: error: assuming pointer wraparound does not occur when comparing P +- C1 with P +- C2 [-Werror=strict-overflow] 322 | if ((unsigned char *) (__cmsg + 1) > ((unsigned char *) __mhdr->msg_control | ^ The line in test_swrap_unit.c:73 is: 73 »·······cmsg = CMSG_NXTHDR(&msg, cmsg); ” This also impacts the out-of-line internal implementation in sysdeps/unix/sysv/linux/cmsg_nxthdr.c. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-02-01 14:55 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-01 14:55 fweimer at redhat dot com [this message] 2022-02-03 15:02 ` [Bug network/28846] " asn at samba dot org 2022-08-03 23:11 ` sam at gentoo dot org 2022-08-03 23:11 ` sam at gentoo dot org 2022-08-03 23:11 ` sam at gentoo dot org 2022-08-04 8:02 ` 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-28846-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).