bug in get_new_inode()

V. Ganesh (ganesh@veritas.com)
Thu, 28 Oct 1999 17:09:42 -0700

hi,
2.3.24 and a few older kernels have a bug in get_new_inode()
in fs/inode.c. if we find the inode in the cache [old = find_inode(..)]
we should __iget(old) rather than __iget(inode).

ganesh

--- linux/fs/inode.c.ORG Thu Oct 28 14:44:09 1999
+++ linux/fs/inode.c Thu Oct 28 15:52:26 1999
@@ -546,7 +546,7 @@

return inode;
}
- __iget(inode);
+ __iget(old);
spin_unlock(&inode_lock);
destroy_inode(inode);
inode = old;

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/