Alexey Kuznetsov ac7f052b9e fuse: fsync() did not return IO errors ... Due to implementation of fuse writeback filemap_write_and_wait_range() does not catch errors. We have to do this directly after fuse_sync_writes() Signed-off-by: Alexey Kuznetsov <kuznet@virtuozzo.com> Signed-off-by: Maxim Patlasov <mpatlasov@virtuozzo.com> Signed-off-by: Miklos Szeredi <mszeredi@redhat.com> Fixes: 4d99ff8f12 ("fuse: Turn writeback cache on") Cc: <stable@vger.kernel.org> # v3.15+		2016-07-29 14:10:57 +02:00
..
Kconfig	fuse: Move CUSE Kconfig entry from fs/Kconfig into fs/fuse/Kconfig	2013-01-17 13:08:45 +01:00
Makefile	CUSE: implement CUSE - Character device in Userspace	2009-06-09 11:24:11 +02:00
control.c	VFS: normal filesystems (and lustre): d_inode() annotations	2015-04-15 15:06:57 -04:00
cuse.c	fuse: Add reference counting for fuse_io_priv	2016-03-14 15:02:51 +01:00
dev.c	fuse: don't mess with blocking signals	2016-07-19 03:08:27 -04:00
dir.c	Use the right predicate in ->atomic_open() instances	2016-07-05 16:02:23 -04:00
file.c	fuse: fsync() did not return IO errors	2016-07-29 14:10:57 +02:00
fuse_i.h	fuse: improve aio directIO write performance for size extending writes	2016-06-30 13:14:10 +02:00
inode.c	fuse: serialize dirops by default	2016-06-30 13:10:49 +02:00