On Thu, May 10, 2012 at 01:29:00PM +0200, maximilian attems wrote: > From: Jan Kara <[email protected]> > > 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 <[email protected]> > Signed-off-by: Jan Kara <[email protected]> > --- > Compile tested on latest Debian 3.2, got shipped in Fedora 15 3.2. > > fs/ext3/ialloc.c | 8 ++++++-- > 1 file changed, 6 insertions(+), 2 deletions(-)
<formletter> This is not the correct way to submit patches for inclusion in the stable kernel tree. Please read Documentation/stable_kernel_rules.txt for how to do this properly. </formletter> -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
