| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20140218112717.GB27965@twins.programming.kicks-ass.net> Date: Tue, 18 Feb 2014 12:27:17 +0100 From: Peter Zijlstra <peterz@...radead.org> To: "xiaofeng.yan" <xiaofeng.yan@...wei.com> Cc: linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...hat.com> Subject: Re: A feature to enhance lockdep function 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 majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists