Hi Andrew - I don't work directly in the glibc community, so I'm not completely familiar with their policies. However, the first step is to get a bug approved upstream so that it can be backported to the 2.23 release (in this case). Adam Conrad at Canonical has volunteered to help us shepherd the patch along, so we hope to be able to expedite it.
We have two possible patches to fix the problem; we are trying to determine which will have the least performance impact. I am hopeful that we can get a decision on that tomorrow so the patch can be put on the libc-alpha list and, we hope, approved without too much difficulty. I will have to defer to Canonical folks (Adam, Matthias) on the process for getting the fix available, but I'm sure this isn't their first rodeo and this shouldn't take too long. My best guess is that the whole process may get done within a week, if all goes well with the community, and a little longer if not. We are definitely not talking months. -- 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
