Comment 1 for bug 1089722

Have you got any examples?
IMHO this can just be a false positive since it's safe to read beyond a buffer end iff:
  * You know you're not crossing a 64bit boundary (since you know you're not crossing a page boundary and hence can't seg)
  * Don't cause any data in that 64bit read to influence the result if it's after the terminating character.

If you've got an example that shows where it breaks either of those two conditions then I agree it's eglibc bug, else I say it's a false positive from valgrind.