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-next>] [day] [month] [year] [list]
Message-ID: <483313DD.2020904@hp.com>
Date:	Tue, 20 May 2008 14:09:33 -0400
From:	"Alan D. Brunelle" <Alan.Brunelle@...com>
To:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: /proc/lock_stat "stuck"

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?

Thanks,
Alan D. Brunelle
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ