| commit | e9d65725bdf5954283625ca4d770bfc34f2ae56a | |
| author | Li Zefan <lizf@cn.fujitsu.com> | |
| Mon, 17 Aug 2009 05:39:49 +0000 (17 13:39 +0800) | ||
| committer | Ingo Molnar <mingo@elte.hu> | |
| Mon, 17 Aug 2009 07:54:40 +0000 (17 09:54 +0200) | ||
| tree | 422219331fb039396ff24d9df6e1d5293cde1bd4 | treesnapshot (tar.gz zip) |
| parent | 212274347fc4d2a7c56bf6c953b02c809e7e0be1 | commitdiff |
lockdep: Fix missing entries in /proc/lock_chains
Two entries are missing in the output of /proc/lock_chains.
One is chains[1]. When lc_next() is called the 1st time,
chains[0] is returned. And when it's called the 2nd time,
chains[2] is returned.
The other missing ons is, when lc_start() is called the 2nd
time, we should start from chains[@pos-1] but not chains[@pos],
because pos == 0 is the header.
Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
Cc: Peter Zijlstra <peterz@infradead.org>
LKML-Reference: <4A88ED25.2040306@cn.fujitsu.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Two entries are missing in the output of /proc/lock_chains.
One is chains[1]. When lc_next() is called the 1st time,
chains[0] is returned. And when it's called the 2nd time,
chains[2] is returned.
The other missing ons is, when lc_start() is called the 2nd
time, we should start from chains[@pos-1] but not chains[@pos],
because pos == 0 is the header.
Signed-off-by: Li Zefan <lizf@cn.fujitsu.com>
Cc: Peter Zijlstra <peterz@infradead.org>
LKML-Reference: <4A88ED25.2040306@cn.fujitsu.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
| kernel/lockdep_proc.c | diffblobblamehistory |