diff options
| author | Florian Weimer <fweimer@redhat.com> | 2019-07-18 20:19:39 +0200 |
|---|---|---|
| committer | Florian Weimer <fweimer@redhat.com> | 2019-07-21 22:31:33 +0200 |
| commit | 87a66e30606ab0e2e45e17eaa862e83dc6013ed6 (patch) | |
| tree | f7006cc5801fbbae6a353bf93746f4b649613727 /malloc/alloc_buffer_alloc_array.c | |
| parent | 719d81f129206d51bf168076ed1578e7414c2506 (diff) | |
| download | glibc-87a66e30606ab0e2e45e17eaa862e83dc6013ed6.tar.xz glibc-87a66e30606ab0e2e45e17eaa862e83dc6013ed6.zip | |
Linux: Use in-tree copy of SO_ constants for !__USE_MISC [BZ #24532]
The kernel changes for a 64-bit time_t on 32-bit architectures
resulted in <asm/socket.h> indirectly including <linux/posix_types.h>.
The latter is not namespace-clean for the POSIX version of
<sys/socket.h>.
This issue has persisted across several Linux releases, so this commit
creates our own copy of the SO_* definitions for !__USE_MISC mode.
The new test socket/tst-socket-consts ensures that the copy is
consistent with the kernel definitions (which vary across
architectures). The test is tricky to get right because CPPFLAGS
includes include/libc-symbols.h, which in turn defines _GNU_SOURCE
unconditionally.
Tested with build-many-glibcs.py. I verified that a discrepancy in
the definitions actually results in a failure of the
socket/tst-socket-consts test.
Diffstat (limited to 'malloc/alloc_buffer_alloc_array.c')
0 files changed, 0 insertions, 0 deletions