[1/6,v2] ext2: fix up error handling for insert_inode_locked

Message ID 4EDEA2C3.60200@redhat.com
State Superseded, archived
Headers show

Commit Message

Eric Sandeen Dec. 6, 2011, 11:18 p.m.
after 250df6ed274d767da844a5d9f05720b804240197
(fs: protect inode->i_state with inode->i_lock), insert_inode_locked()
no longer returns the inode with I_NEW set on failure.  However,
the error handler still calls unlock_new_inode() on failure,
which does a WARN_ON if I_NEW is not set, so any failure spews
a lot of warnings.

(We also were doing dquot_drop, etc before we had initialized
the quota, that gets skipped as well)

Signed-off-by: Eric Sandeen <sandeen@redhat.com>

V2: don't rearrange clear_nlink, and edit commit message.

To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


diff --git a/fs/ext2/ialloc.c b/fs/ext2/ialloc.c
index c4e81df..06cbc22 100644
--- a/fs/ext2/ialloc.c
+++ b/fs/ext2/ialloc.c
@@ -574,7 +574,7 @@  got:
 	if (insert_inode_locked(inode) < 0) {
 		err = -EINVAL;
-		goto fail_drop;
+		goto fail_put;
@@ -603,6 +603,7 @@  fail_drop:
 	inode->i_flags |= S_NOQUOTA;
 	return ERR_PTR(err);