linux-kernel - Re: [PATCH] tracing: Rename lockdep event subsystem into lock

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: <1258103409.4039.1079.camel@laptop>
Date:	Fri, 13 Nov 2009 10:10:09 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	Ingo Molnar <mingo@...e.hu>, LKML <linux-kernel@...r.kernel.org>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Mike Galbraith <efault@....de>,
	Paul Mackerras <paulus@...ba.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Li Zefan <lizf@...fujitsu.com>,
	Hitoshi Mitake <mitake@....info.waseda.ac.jp>
Subject: Re: [PATCH] tracing: Rename lockdep event subsystem into lock

On Fri, 2009-11-13 at 10:06 +0100, Frederic Weisbecker wrote:
> Lockdep events subsystem gathers various locking related events such
> as a request, release, contention or acquisition of a lock.
> 
> The name of this event subsystem is a bit of a misnomer since these
> events are not quite related to lockdep but more generally to locking,
> ie: these events are not reporting lock dependencies or possible
> deadlock scenario but pure locking events.

But in order to get them you need pretty much all of lockdep, except
PROVE_LOCKING. You get all the lock debugging, the lock tracking, the
struct dep_map bloat etc.

But sure, I don't mind renaming the category.

--
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/