aboutsummaryrefslogtreecommitdiffstats
path: root/fs/ubifs/debug.h
diff options
context:
space:
mode:
authorArtem Bityutskiy <Artem.Bityutskiy@nokia.com>2011-04-26 10:21:54 +0300
committerArtem Bityutskiy <Artem.Bityutskiy@nokia.com>2011-05-13 19:23:56 +0300
commitec0681426526b23d3e12cf247d64676806c30b7f (patch)
tree181b2a911800e86e48c40c2846291ac3e7a9df80 /fs/ubifs/debug.h
parentUBIFS: print useful debugging messages when cannot recover gc_lnum (diff)
downloadlinux-dev-ec0681426526b23d3e12cf247d64676806c30b7f.tar.xz
linux-dev-ec0681426526b23d3e12cf247d64676806c30b7f.zip
UBIFS: dump the stack on errors in failure mode too
When UBIFS is in the failure mode (used for power cut emulation testing) we for some reasons do not dump the stack in many places, e.g., in assertions. Probably at early days we had too many of them and disabled this to make the development easier, but then never enabled. Nowadays I sometimes observe assertion failures during power cut testing, but the useful stackdump is not printed, which is bad. This patch makes UBIFS always print the stackdump when debugging is enabled. Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
Diffstat (limited to 'fs/ubifs/debug.h')
-rw-r--r--fs/ubifs/debug.h5
1 files changed, 1 insertions, 4 deletions
diff --git a/fs/ubifs/debug.h b/fs/ubifs/debug.h
index 8934c12f108e..f3e235fcd8df 100644
--- a/fs/ubifs/debug.h
+++ b/fs/ubifs/debug.h
@@ -107,10 +107,7 @@ struct ubifs_debug_info {
} \
} while (0)
-#define dbg_dump_stack() do { \
- if (!dbg_failure_mode) \
- dump_stack(); \
-} while (0)
+#define dbg_dump_stack() dump_stack()
/* Generic debugging messages */
#define dbg_msg(fmt, ...) do { \