jffs2: fix up error handling for insert_inode_locked
authorEric Sandeen <sandeen@sandeen.net>
Tue, 6 Dec 2011 23:06:06 +0000 (17:06 -0600)
committerDavid Woodhouse <David.Woodhouse@intel.com>
Mon, 9 Jan 2012 18:18:03 +0000 (18:18 +0000)
commit53466710202900ce49e471f480cac11275e1d0c4
treec9a4d9458dff37cd7e15f2181c8bc1d5edcf3f91
parentfa3ae714c763f3e9d8fd876879338d2b674b8db2
jffs2: fix up error handling for insert_inode_locked

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 can just drop the unlock_new_inode() if insert_inode_locked()
fails here.

Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@linux.intel.com>
Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
fs/jffs2/fs.c