Jeff Layton 0ae3fa4dc1 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>
2019-05-07 23:24:55 -05:00
..
2018-06-12 16:19:22 -07:00
2019-03-14 19:32:36 -05:00
2019-03-06 21:55:12 -06:00
2019-03-04 20:05:34 -06:00
2018-12-28 10:05:58 -06:00
2018-08-07 14:15:41 -05:00
2019-03-14 19:32:36 -05:00
2019-01-24 09:37:33 -06:00
2013-09-08 14:54:24 -05:00