Bug#625521: glibc: causes segfault in Xorg
Le 04/05/2011 07:43, Jonathan Nieder a écrit :
> clone 625521 -1
> severity 625521 grave
> severity -1 important
> reassign -1 libc6 2.13-0exp1
> retitle -1 glibc: memcpy copies down on amd64
> tags -1 upstream patch fixed-upstream
> # sorry for the noise
> quit
>
> Jonathan Nieder wrote:
>
>> Sounds like http://sourceware.org/bugzilla/show_bug.cgi?id=12518
>> which is fixed (sort of) by commit 0354e355 (2011-04-01).
Are you sure this is related? I find strange a recent version of xorg is
still not fixed
> By the way, in principle that might be a nice commit to cherry-pick.
>
> Not sure how to do it safely, though --- backing out the amd64
> optimization would hide important bugs that can cause suffering later,
> while applying upstream's fix would mean that apps linked against libc
> would use new ABI.
No, it's not something possible to cherry-pick as it is based on symbol
versioning from version 2.14. Also it only really apply to binary-only
distribution, in Debian as soon as your rebuild the package, it will use
the new 2.14 symbols, and memcpy instead of memmove.
> I guess reverting glibc-2.13~215 (Improve 64bit memcpy/memmove for
> Atom, Core 2 and Core i7, 2010-06-30) in sid (but not experimental)
> and encouraging people to test libc6/experimental might be a good way.
I don't think we can really keep a version in experimental just for
that. And reverting that patch means nobody will complain, and issues
will never be fixed.
> Do you know how soon upstream's planning to release 2.14?
>
It used to be every 6 months (so around september), but it is not sure
it continues to be like that.
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
Reply to: