On Mon, Jan 26, 2015 at 06:46:12PM -0500, Sasha Levin wrote: > This seems to cause the following lockdep warning:
unlikely, the fork -> sched_move_task() was only used to establish that rq->lock nests inside p->pi_lock, and there's a gazillion other ways to establish that. That said, its a right mess indeed. Let me stare a wee bit more at this rats nets. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
