On Mon, Jun 13, 2016 at 07:09:33AM +0200, Florian Weimer wrote: > glibc upstream, during development of the 2.24 release, introduced new > symbol versions recvmsg@GLIBC_2.24, sendmsg@GLIBC_2.24 (and > recvmmsg@GLIBC_2.24, sendmmsg@GLIBC_2.24 on 64-bit architectures), in order > to fix some minor POSIX compliance issue. (POSIX and the Linux kernel > disagree about the width of some fields in struct msghdr.) These changes > landed in rawhide as part of glibc-2.23.90-19.fc25. > > This change caused quite a few issues (chrony stopped building, Address > Sanitizer interception of these functions was affected, probably more). > Considering that the deviation from POSIX was really minor, this was > considered a poor trade-off, and the patch and ABI change was eventually > reverted upstream. Do you have a pointer to the glibc change, or specific details about what exactly changed. It looks like the change broke libvirt usage of SCM_RIGHTS, and despite fact that you're reverting it in glibc, I'm wondering if there is non-standards compliant usage in libvirt that we should be fixing regardless. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
