From: Meelis Roos <mroos@xxxxxxxx> Date: Fri, 17 Oct 2014 14:12:09 +0300 (EEST) > However, on top of mainline HEAD 3.17.0-09670-g0429fbc it explodes with > scheduler BUG - just reported to LKML + sched maintainers. task_stack_end_corrupted() cannot work properly on sparc64. It stores the magic value at "task_thread_info(p) + 1", but on sparc64 that's where we store the nested array of FPU register saves. In fact this facility could be corrupting FPU register state in certain circumstances. The current sparc64 design is intentional, the CPU stack grows down toward the thread_info, and the FPU stack saving area grows up from the end of thread_info. I don't want to define the array size of the fpregs save area explicitly and thereby placing an artificial limit there. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>