summaryrefslogtreecommitdiff
path: root/fs/ubifs/debug.h
diff options
context:
space:
mode:
authorArtem Bityutskiy <artem.bityutskiy@linux.intel.com>2012-05-16 20:04:54 +0400
committerArtem Bityutskiy <artem.bityutskiy@linux.intel.com>2012-05-16 20:04:54 +0400
commit7c46d0ae29ba880963db283706950de7aa86c0a0 (patch)
tree1ba1ba22f2281dda27116443db50ebbcfc84cc09 /fs/ubifs/debug.h
parent1bdcc63112a0fe10030abee6ad71aaecd091e68e (diff)
downloadlinux-7c46d0ae29ba880963db283706950de7aa86c0a0.tar.xz
UBIFS: get rid of dbg_dump_stack
In case of errors we almost always need the stack dump - it makes no sense to compile it out. Remove the 'dbg_dump_stack()' function completely. Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.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 9f717655df18..6e5d345a0f7e 100644
--- a/fs/ubifs/debug.h
+++ b/fs/ubifs/debug.h
@@ -149,7 +149,7 @@ struct ubifs_global_debug_info {
if (unlikely(!(expr))) { \
printk(KERN_CRIT "UBIFS assert failed in %s at %u (pid %d)\n", \
__func__, __LINE__, current->pid); \
- dbg_dump_stack(); \
+ dump_stack(); \
} \
} while (0)
@@ -161,8 +161,6 @@ struct ubifs_global_debug_info {
} \
} while (0)
-#define dbg_dump_stack() dump_stack()
-
#define dbg_err(fmt, ...) do { \
ubifs_err(fmt, ##__VA_ARGS__); \
} while (0)
@@ -341,7 +339,6 @@ void dbg_debugfs_exit_fs(struct ubifs_info *c);
printk(KERN_DEBUG fmt "\n", ##__VA_ARGS__); \
} while (0)
-#define dbg_dump_stack()
#define ubifs_assert_cmt_locked(c)
#define dbg_msg(fmt, ...) ubifs_dbg_msg(fmt, ##__VA_ARGS__)