Yes, that's the one. Interestingly, in glibc-2.19, this change is reverted. It is present in glibc-2.17 & glibc-2.18 as released by GNU. Oddly, in glibc git, the buggy version appears.
I've filed a bug with glibc [1] and let the author know that there is a problem. In the meantime, I'll try to figure out what the problem is. I think we may need to file a debian bug though since it will require a glibc update. Sebastien, can you handle that?