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
| ||
|
Date: Wed, 3 Jan 2007 15:59:28 -0800 From: "Chen, Tim C" <tim.c.chen@...el.com> To: "Bill Huey \(hui\)" <billh@...ppy.monkey.org>, "Ingo Molnar" <mingo@...e.hu> Cc: <linux-kernel@...r.kernel.org>, "Siddha, Suresh B" <suresh.b.siddha@...el.com>, "Peter Zijlstra" <a.p.zijlstra@...llo.nl>, "Steven Rostedt" <rostedt@...dmis.org>, "Thomas Gleixner" <tglx@...utronix.de>, "Daniel Walker" <dwalker@...sta.com> Subject: RE: [PATCH] lock stat for -rt 2.6.20-rc2-rt2.2.lock_stat.patch Bill Huey (hui) wrote: > > Patch here: > > http://mmlinux.sourceforge.net/public/patch-2.6.20-rc2-rt2.2.lock_stat.p atch > > bill This version is much better and ran stablely. If I'm reading the output correctly, the locks are listed by their initialization point (function, file and line # that a lock is initialized). That's good information to identify the lock. However, it will be more useful if there is information about where the locking was initiated from and who was trying to obtain the lock. Tim - 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