workaround for glibc bug

[Maksim Orlovich]

> Distributions probably can backport the solution. I won't comment on how
> trivial or complex that task is. That's why we need to get the word out
> now,
> so that they have time to do it.

Does anyone here have a good contact/working relation with the glibc
development community? I would guess 2.6.90 is a development version
for 2.7; and it may be good to ask them to at least consider backporting
it to 2.6.x. Certainly the glibc developers should at least be able to
comment on the feasibility and sanity of backports for the fix.