On Thu, May 10, 2012 at 07:05:46AM -0700, Greg KH wrote: > On Thu, May 10, 2012 at 01:30:00PM +0200, maximilian attems wrote: > > From: Jan Kara <[email protected]> > > > > 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 <[email protected]> > > Signed-off-by: "Theodore Ts'o" <[email protected]> > > --- > > Compile tested on latest Debian 3.2, got shipped in Fedora 15 3.2. > > > > fs/ext4/ialloc.c | 8 ++++++-- > > 1 file changed, 6 insertions(+), 2 deletions(-) > > <formletter> > > </formletter>
This is acd6ad83517639e8f09a8c5525b1dccd81cd2a10 -- 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
