linux-kernel - Re: /proc/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: <1211361380.6463.63.camel@lappy.programming.kicks-ass.net>
Date:	Wed, 21 May 2008 11:16:20 +0200
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	"Alan D. Brunelle" <Alan.Brunelle@...com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: /proc/lock_stat "stuck"

On Tue, 2008-05-20 at 14:09 -0400, Alan D. Brunelle wrote:
> I'm attempting to use /proc/lock_stat to gather some information during
> some benchmarking runs, but what I find happens is as follows:
> 
> 1. I boot the system - 2.6.26-rc3 kernel + CONFIG_LOCK_STAT=y
> 
> 2. I can then look at /proc/lock_stat, and it has valid-looking values
> 
> 3. I wait a while, do some stuff, but when I look at /proc/lock_stat
> again the values have not changed.
> 
> 4. If I clear the counters - echo 0 > /proc/lock_stat - the counters
> never increase, and no information besides the headers are output when I
> cat /proc/lock_stat.
> 
> 
> Is there something that one needs to do to get counter updates?

Did you get lockdep warnings? Those disable all lock debugging,
including lockstat.

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