On Thu, Dec 08, 2011 at 09:28:34PM +0100, Jan Kara wrote: > When insert_inode_locked() fails in ext4_new_inode() it most likely means inode > bitmap got corrupted and we allocated again inode which is already in use. Also > doing unlock_new_inode() during error recovery is wrong since the inode does > not have I_NEW set. Fix the problem by jumping to fail: (instead of fail_drop:) > which declares filesystem error and does not call unlock_new_inode(). > > Signed-off-by: Jan Kara <jack@xxxxxxx> Applied, thanks. - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
