summaryrefslogtreecommitdiff
path: root/fs
diff options
context:
space:
mode:
authorArtem Bityutskiy <artem.bityutskiy@linux.intel.com>2012-01-10 19:32:30 +0200
committerGreg Kroah-Hartman <gregkh@suse.de>2012-01-25 16:13:25 -0800
commit6aeb366d6a7e5cc3c2ab1666751c493c9c3e87e5 (patch)
treea5a8e327aa675bc8eed719ca5089342493445c48 /fs
parentf15be6f6ce84f1e776abfe51bf52f3aaf4d4e5e9 (diff)
downloadkernel-common-6aeb366d6a7e5cc3c2ab1666751c493c9c3e87e5.tar.gz
kernel-common-6aeb366d6a7e5cc3c2ab1666751c493c9c3e87e5.tar.bz2
kernel-common-6aeb366d6a7e5cc3c2ab1666751c493c9c3e87e5.zip
UBIFS: fix debugging messages
commit d34315da9146253351146140ea4b277193ee5e5f upstream. Patch 56e46742e846e4de167dde0e1e1071ace1c882a5 broke UBIFS debugging messages: before that commit when UBIFS debugging was enabled, users saw few useful debugging messages after mount. However, that patch turned 'dbg_msg()' into 'pr_debug()', so to enable the debugging messages users have to enable them first via /sys/kernel/debug/dynamic_debug/control, which is very impractical. This commit makes 'dbg_msg()' to use 'printk()' instead of 'pr_debug()', just as it was before the breakage. Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'fs')
-rw-r--r--fs/ubifs/debug.h5
1 files changed, 4 insertions, 1 deletions
diff --git a/fs/ubifs/debug.h b/fs/ubifs/debug.h
index 8d9c46810189..3f6582995ca8 100644
--- a/fs/ubifs/debug.h
+++ b/fs/ubifs/debug.h
@@ -190,7 +190,10 @@ extern spinlock_t dbg_lock;
} while (0)
/* Just a debugging messages not related to any specific UBIFS subsystem */
-#define dbg_msg(fmt, ...) ubifs_dbg_msg("msg", fmt, ##__VA_ARGS__)
+#define dbg_msg(fmt, ...) \
+ printk(KERN_DEBUG "UBIFS DBG (pid %d): %s: " fmt "\n", current->pid, \
+ __func__, ##__VA_ARGS__)
+
/* General messages */
#define dbg_gen(fmt, ...) ubifs_dbg_msg("gen", fmt, ##__VA_ARGS__)
/* Additional journal messages */