summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJens Axboe <axboe@suse.de>2006-06-08 10:26:39 +0200
committerLinus Torvalds <torvalds@g5.osdl.org>2006-06-08 15:14:24 -0700
commit71601e2b33dad9acb8d7844f7321f90ed9d1bce8 (patch)
tree5057391f7c99e207ca8a18c075bc2333b57d3e7f
parentbc1c116974a5c3f498112a6f175d3e4a8cd5bdbc (diff)
downloadop-kernel-dev-71601e2b33dad9acb8d7844f7321f90ed9d1bce8.zip
op-kernel-dev-71601e2b33dad9acb8d7844f7321f90ed9d1bce8.tar.gz
[PATCH] debugfs inode leak
Looking at the reiser4 crash, I found a leak in debugfs. In debugfs_mknod(), we create the inode before checking if the dentry already has one attached. We don't free it if that is the case. These bugs happen quite often, I'm starting to think we should disallow such coding in CodingStyle. Signed-off-by: Jens Axboe <axboe@suse.de> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-rw-r--r--fs/debugfs/inode.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/fs/debugfs/inode.c b/fs/debugfs/inode.c
index 85d166c..b55b4ea 100644
--- a/fs/debugfs/inode.c
+++ b/fs/debugfs/inode.c
@@ -67,12 +67,13 @@ static struct inode *debugfs_get_inode(struct super_block *sb, int mode, dev_t d
static int debugfs_mknod(struct inode *dir, struct dentry *dentry,
int mode, dev_t dev)
{
- struct inode *inode = debugfs_get_inode(dir->i_sb, mode, dev);
+ struct inode *inode;
int error = -EPERM;
if (dentry->d_inode)
return -EEXIST;
+ inode = debugfs_get_inode(dir->i_sb, mode, dev);
if (inode) {
d_instantiate(dentry, inode);
dget(dentry);
OpenPOWER on IntegriCloud