Hi, We also have experienced this issue with 3.2.0-57-generic. Thanks to the core dump analysis by Louis Bouchard, I could notice that accessing current->mempolicy in interrupt context is totally bad idea, and then found the following commit.
http://git.kernel.org/cgit/linux/kernel/git/stable/linux- stable.git/commit/?id=e7b691b085fda913830e5280ae6f724b2a63c824 This fix was introduced in 3.6-rc1, that's why 3.8 kernel hasn't experienced this issue. Can you backport the fix to 12.04's 3.2 kernel? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1233175 Title: Kernel panic : mempolicy potential use-after-free on server running mongodb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1233175/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
