cifs: remove superfluous inode_lock in cifs_{strict_}fsync
authorJeff Layton <jlayton@kernel.org>
Mon, 8 Apr 2019 14:59:42 +0000 (10:59 -0400)
committerSteve French <stfrench@microsoft.com>
Wed, 8 May 2019 04:24:55 +0000 (23:24 -0500)
commit0ae3fa4dc1fcb94b2e992b222dc47781b0414076
treec1f33e27660b7bf1c987716a6475057c57a03b7b
parent214bab448476dbfb63f55f5afaa93d3894d85233
cifs: remove superfluous inode_lock in cifs_{strict_}fsync

Originally, filemap_write_and_wait took the i_mutex internally, but
commit 02c24a82187d pushed the mutex acquisition into the individual
fsync routines, leaving it up to the subsystem maintainers to remove
it if it wasn't needed.

For cifs, I see no reason to take the inode_lock here. All of the
operations inside that lock are protected in other ways.

Signed-off-by: Jeff Layton <jlayton@kernel.org>
Signed-off-by: Steve French <stfrench@microsoft.com>
Acked-by: Pavel Shilovsky <pshilov@microsoft.com>
fs/cifs/file.c