Hi Bill - Thanks for the glibc bug link.
Totally understand about people being out, not a problem. However, I'm not very familiar with the development process for upstream glibc fixes to make their way into an LTS release. Do you have a rough estimate of the timeline for that landing in something that we can pull in via apt-get update? Are we talking days, weeks, months? My expectation right now is that we are going to continue forward with issuing the MongoDB 3.4 GA on POWER Ubuntu 16.04, and relnote this issue, probably stating that MongoDB 3.4 should not be run in production on POWER Ubuntu 16.04 unless glibc has been upgraded to version X or newer. We might even add a server startup warning, if it will be possible for us to detect at runtime that we are running with an affected glibc. I'd imagine that might prove difficult if this comes in as an Ubuntu patch to the existing libc version though. Thoughts on that? Andrew -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1640518 Title: MongoDB Memory corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1640518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
