glibc 2.34 32bit armhf segfaults with ping ::1 (recvmsg)
Bug #1947404 reported by
msaxl
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| glibc (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
see
https:/
in short the 32 to 64 bit timestamp emulation messes up the cmsg of the received packet (half-overwrites a cmsg struct instead of appending it)
| summary: |
- giblc 2.35 impish 32bit armhf glibc segfaults with ping ::1 (recvmsg) + giblc 2.34 impish 32bit armhf glibc segfaults with ping ::1 (recvmsg) |
| summary: |
- giblc 2.34 impish 32bit armhf glibc segfaults with ping ::1 (recvmsg) + glibc 2.34 impish 32bit armhf glibc segfaults with ping ::1 (recvmsg) |
| summary: |
- glibc 2.34 impish 32bit armhf glibc segfaults with ping ::1 (recvmsg) + glibc 2.34 impish 32bit armhf segfaults with ping ::1 (recvmsg) |
| summary: |
- glibc 2.34 impish 32bit armhf segfaults with ping ::1 (recvmsg) + glibc 2.34 impish/jammy 32bit armhf segfaults with ping ::1 (recvmsg) |
Revision history for this message
| msaxl (saxl) wrote Re: glibc 2.34 impish/jammy 32bit armhf segfaults with ping ::1 (recvmsg) | #1 |
Revision history for this message
| msaxl (saxl) wrote | #2 |
| summary: |
- glibc 2.34 impish/jammy 32bit armhf segfaults with ping ::1 (recvmsg) + glibc 2.34 32bit armhf segfaults with ping ::1 (recvmsg) |
To post a comment you must log in.
it seems to be fixed in 2.35
The relevant diffs are:
https:/
https:/
I will try to build it for impish,
but glibc is currently not buildable on jammy itself (and by the way i386 does not build on amd's cpus, only intel), but that is not a user problem..