Christoph Hellwig 45dd052e67 fs: handle FIEMAP_FLAG_SYNC in fiemap_prep ... By moving FIEMAP_FLAG_SYNC handling to fiemap_prep we ensure it is handled once instead of duplicated, but can still be done under fs locks, like xfs/iomap intended with its duplicate handling. Also make sure the error value of filemap_write_and_wait is propagated to user space. Signed-off-by: Christoph Hellwig <hch@lst.de> Reviewed-by: Amir Goldstein <amir73il@gmail.com> Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com> Link: https://lore.kernel.org/r/20200523073016.2944131-8-hch@lst.de Signed-off-by: Theodore Ts'o <tytso@mit.edu>		2020-06-03 23:16:55 -04:00
..
alloc.c
alloc.h
bmap.c
bmap.h
btnode.c
btnode.h
btree.c
btree.h
cpfile.c
cpfile.h
dat.c
dat.h
dir.c
direct.c
direct.h
export.h
file.c
gcinode.c
ifile.c
ifile.h
inode.c	fs: handle FIEMAP_FLAG_SYNC in fiemap_prep	2020-06-03 23:16:55 -04:00
ioctl.c
Kconfig
Makefile
mdt.c
mdt.h
namei.c
nilfs.h
page.c
page.h
recovery.c
segbuf.c
segbuf.h
segment.c
segment.h
sufile.c
sufile.h
super.c
sysfs.c
sysfs.h
the_nilfs.c
the_nilfs.h