linux-kernel - Re: [PATCH] lockdep: lock contention tracking

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: <20070521093639.GA29025@elte.hu>
Date:	Mon, 21 May 2007 11:36:39 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Bill Huey <billh@...ppy.monkey.org>
Cc:	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	linux-kernel@...r.kernel.org, Jason Baron <jbaron@...hat.com>,
	Steven Rostedt <rostedt@...dmis.org>
Subject: Re: [PATCH] lockdep: lock contention tracking

* Bill Huey <billh@...ppy.monkey.org> wrote:

> I write lockstat without the knowledge that lockdep was replicating 
> the same work and I audited 1600 something lock points in the kernel 
> to convert the usage of C99 style initializers to something more 
> regular.

you got the history wrong i think: the first version of lockdep was 
released to lkml a year ago (May 2006), while the first time you 
mentioned your lock contention patch was November 2006 and you released 
it to lkml in December 2006 - so it was _you_ who was "replicating the 
same work", not lockdep :-) And this was pointed out to you very early 
on, many months ago.

and regarding C99 style lock initializers: the -rt project has been 
removing a whole heap of them in the past 2.5 years, since Oct 2004 or 
so, and regularly cleansed the upstream kernel for old-style 
initializers ever since then - so i'm not sure what you are referring 
to.

> I also did this without consideration of things like debuginfo since I 
> don't use those things.

btw., you dont even need CONFIG_DEBUG_INFO to get usable symbol names, 
CONFIG_KALLSYMS alone will do it too. (It's only if you really cannot 
tell from the lock symbol name and the function name what the entry is 
about - which is very rare - that you need to look at any debug-info)

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