On Tue, Feb 18, 2014 at 06:26:33PM +0800, xiaofeng.yan wrote: > From the above information we can get what does really matter rapidly > when hung-task information. > This case may be simple. Developer couldn't know the reason why > hung-task happen in complex environment. > > I don't know whether this feature is helpful or not in debug stage.
So we already print the held lock information, and its usually pretty clear which lock we're trying to grab from the stack trace, which is also already printed. -- 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/
