Message ID | 1323a2735a9106cf0fa1a6ffee938ce432aa085d.1356117764.git.luto@amacapital.net |
---|---|
State | Accepted, archived |
Headers | show |
On Fri, Dec 21, 2012 at 11:24:58AM -0800, Andy Lutomirski wrote: > i_mutex is not held when ->sync_file is called. > > Reviewed-by: Jan Kara <jack@suse.cz> > Signed-off-by: Andy Lutomirski <luto@amacapital.net> Thanks, applied. - Ted -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/fs/ext4/fsync.c b/fs/ext4/fsync.c index be1d89f..8c15642 100644 --- a/fs/ext4/fsync.c +++ b/fs/ext4/fsync.c @@ -113,8 +113,6 @@ static int __sync_inode(struct inode *inode, int datasync) * * What we do is just kick off a commit and wait on it. This will snapshot the * inode to disk. - * - * i_mutex lock is held when entering and exiting this function */ int ext4_sync_file(struct file *file, loff_t start, loff_t end, int datasync)