On Wed, Nov 23, 2011 at 04:53:31PM +0800, Cong Wang wrote: > +int vmtruncate_file_range(struct file *file, struct inode *inode, > + loff_t lstart, loff_t lend) We can always get the inode from file->f_path.dentry->d_inode, thus passing both of them doesn't make much sense. > + if (!file->f_op->fallocate) > return -ENOSYS; > > mutex_lock(&inode->i_mutex); > inode_dio_wait(inode); > unmap_mapping_range(mapping, holebegin, holelen, 1); > - inode->i_op->truncate_range(inode, lstart, lend); > + mutex_unlock(&inode->i_mutex); > + > + err = do_fallocate(file, FALLOC_FL_KEEP_SIZE|FALLOC_FL_PUNCH_HOLE, > + holebegin, holelen); > + if (err) > + return err; > + > + mutex_lock(&inode->i_mutex); > /* unmap again to remove racily COWed private pages */ > unmap_mapping_range(mapping, holebegin, holelen, 1); > mutex_unlock(&inode->i_mutex); I suspect this should be turned inside out, just we do for normal truncate. That is instead of keeping vmtruncate(_file)_range we should have a truncate_pagecache_range do to the actual zapping, closely mirroring what we do for truncate. In the best case we'd even implement the regular truncate ones on top of the range version. It also seems like all fallocate implementaions for far got away without the unmap_mapping_range, so either people didn't test them hard enough, or tmpfs doesn't need it either. I fear the former is true. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
