On Fri, 4 May 2007, Pekka J Enberg wrote: > Index: 2.6/fs/ext3/super.c > =================================================================== > --- 2.6.orig/fs/ext3/super.c 2007-05-04 12:57:09.000000000 +0300 > +++ 2.6/fs/ext3/super.c 2007-05-04 13:01:27.000000000 +0300 > @@ -444,17 +444,26 @@ static struct kmem_cache *ext3_inode_cac > static struct inode *ext3_alloc_inode(struct super_block *sb) > { > struct ext3_inode_info *ei; > + struct inode *inode; > > ei = kmem_cache_alloc(ext3_inode_cachep, GFP_NOFS); > if (!ei) > return NULL; > + INIT_LIST_HEAD(&ei->i_orphan); > +#ifdef CONFIG_EXT3_FS_XATTR > + init_rwsem(&ei->xattr_sem); > +#endif > + mutex_init(&ei->truncate_mutex);
^^^ whitespace issues Also could this be generalized to also apply to the generic inode allocation in fs/inode.c? - To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html