Hi all, I have seen this bug crash the kernel when the security framework is enabled in the kernel config. It crashed with a bad syscall from the events/0 workqueue; probably because the security framework is initialized very early and thus the stack has been used more [or differently] and we end up picking up a bad [nonzero] arbitrary address from the stack. best regards, Viktor -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
