diff options
author | Manish Katiyar <mkatiyar@gmail.com> | 2009-09-18 13:05:43 -0700 |
---|---|---|
committer | Al Viro <viro@zeniv.linux.org.uk> | 2009-09-24 07:47:24 -0400 |
commit | af0d9ae811d11de8a01d6bc922c5e062be01bd7f (patch) | |
tree | ee54e986a83208c625919904c39804da48076492 | |
parent | 14be27460e4722d7135de3c46d043b4fc4382247 (diff) | |
download | linux-3.10-af0d9ae811d11de8a01d6bc922c5e062be01bd7f.tar.gz linux-3.10-af0d9ae811d11de8a01d6bc922c5e062be01bd7f.tar.bz2 linux-3.10-af0d9ae811d11de8a01d6bc922c5e062be01bd7f.zip |
fs/inode.c: add dev-id and inode number for debugging in init_special_inode()
Add device-id and inode number for better debugging. This was suggested
by Andreas in one of the threads
http://article.gmane.org/gmane.comp.file-systems.ext4/12062 .
"If anyone has a chance, fixing this error message to be not-useless would
be good... Including the device name and the inode number would help
track down the source of the problem."
Signed-off-by: Manish Katiyar <mkatiyar@gmail.com>
Cc: Andreas Dilger <adilger@sun.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
-rw-r--r-- | fs/inode.c | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/fs/inode.c b/fs/inode.c index 76582b06ab9..07d775ea616 100644 --- a/fs/inode.c +++ b/fs/inode.c @@ -1599,7 +1599,8 @@ void init_special_inode(struct inode *inode, umode_t mode, dev_t rdev) else if (S_ISSOCK(mode)) inode->i_fop = &bad_sock_fops; else - printk(KERN_DEBUG "init_special_inode: bogus i_mode (%o)\n", - mode); + printk(KERN_DEBUG "init_special_inode: bogus i_mode (%o) for" + " inode %s:%lu\n", mode, inode->i_sb->s_id, + inode->i_ino); } EXPORT_SYMBOL(init_special_inode); |