linux-kernel - Re: [RFC 1/4] lockdep: additional lock specific information when dumping locks

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150112150633.GD25256@twins.programming.kicks-ass.net>
Date:	Mon, 12 Jan 2015 16:06:33 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Sasha Levin <sasha.levin@...cle.com>
Cc:	linux-kernel@...r.kernel.org, mingo@...hat.com
Subject: Re: [RFC 1/4] lockdep: additional lock specific information when
 dumping locks

On Mon, Jan 12, 2015 at 09:57:08AM -0500, Sasha Levin wrote:
> When dumping held locks, it might be useful to get additional lock-specific
> information about each lock.
> 
> This is mainly useful to figure out who really holds each lock rather then
> who's just waiting on it, but it could be extended further or extended to
> the other lockdep users if required.

I really don't see the point in this; I would much rather have something
useful like:

 http://lwn.net/Articles/579849/
--
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/