diff options
author | Ingo Molnar <mingo@elte.hu> | 2006-10-17 00:09:28 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@g5.osdl.org> | 2006-10-17 08:18:42 -0700 |
commit | ca268c691de95612981b93e58899c1d73fdb6b47 (patch) | |
tree | 5bffd6512113613ae9c3dfd0e8b19a14d8e64856 /kernel/power | |
parent | 623a43952abfad2d48f287d1fab07b2089d07554 (diff) | |
download | kernel_samsung_tuna-ca268c691de95612981b93e58899c1d73fdb6b47.zip kernel_samsung_tuna-ca268c691de95612981b93e58899c1d73fdb6b47.tar.gz kernel_samsung_tuna-ca268c691de95612981b93e58899c1d73fdb6b47.tar.bz2 |
[PATCH] lockdep: increase max allowed recursion depth
In general, lockdep warnings are intended to be non-fatal, so I have put in
various practical limits on internal data structure failure modes. We haven't
had a /single/ lockdep-internal crash ever since lockdep went upstream [the
unwinder crashes are outside of lockdep], and that's largely due to the good
internal checks it does.
Recursion within the dependency graph is currently limited to 20, that's
probably not enough on some many-CPU boxes - this patch doubles it to 40. I
have written the lockdep functions to have as small stackframes as possible,
so 40 should be OK too. (The practical recursion limit should be somewhere
between 100 and 200 entries. If we hit that then I'll change the algorithm to
be iteration-based. Graph walking logic is so easy to program via recursion,
so i'd like to keep recursion as long as possible.)
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'kernel/power')
0 files changed, 0 insertions, 0 deletions