tree fb98d05d5fa83202d7b4bead058826366fc2592e
parent d03e1292c46721f60830c5d2e334966472002ed0
author Jan Kara <jack@suse.cz> 1323375226 +0100
committer Jan Kara <jack@suse.cz> 1326113527 +0100

ext3: Fix error handling on inode bitmap corruption

When insert_inode_locked() fails in ext3_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 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().

Reviewed-by: Eric Sandeen <sandeen@redhat.com>
Signed-off-by: Jan Kara <jack@suse.cz>