We're currently working with ARM's kernel tree, see: http://www.linux-arm.org/
To clarify my expectation: there's no direct benefit to your applying this to your tree right now, since you don't support the affected platforms yet; but it seemed worth flagging the issue up to you so you're aware. It may be needed in the future because this patch is not in mainline yet and may take a long time to propagate via that path. I should note: there was never any userspace bug causing the crash --- it's a bit of obscure behaviour which is currently handled properly neither in userspace or in the kernel. Karmic works around it as a side effect of the migration to eglibc, but this may be just a fortunate coincidence. Whether Karmic's userspace works in all cases is unknown: init (and other straightforward PIE executables) does't crash any more, but there's a fair chance that at least one other package somewhere may be manipulating mmap'd memory in a way which will be vulnerable to the same class of bug. You may have a better understanding of the risks, but I don't know myself without a lot more investigation. So you can apply the patch directly if you think it makes sense for you; otherwise can the issue be tracked for future reference somehow? Hope that clarifies things— apologies for any confusion there. -- On ARM platforms with write-allocate caches, I-cache may be populated with garbage after copy-on-write page duplication https://bugs.launchpad.net/bugs/426280 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
