linux

iv/linux

History

Eric Sandeen 0357794830 exfat: use iter_file_splice_write

Doing copy_file_range() on exfat with a file opened for direct IO leads
to an -EFAULT:

# xfs_io -f -d -c "truncate 32768" \
       -c "copy_range -d 16384 -l 16384 -f 0" /mnt/test/junk
copy_range: Bad address

and the reason seems to be that we go through:

default_file_splice_write
 splice_from_pipe
  __splice_from_pipe
   write_pipe_buf
    __kernel_write
     new_sync_write
      generic_file_write_iter
       generic_file_direct_write
        exfat_direct_IO
         do_blockdev_direct_IO
          iov_iter_get_pages

and land in iterate_all_kinds(), which does "return -EFAULT" for our kvec
iter.

Setting exfat's splice_write to iter_file_splice_write fixes this and lets
fsx (which originally detected the problem) run to success from
the xfstests harness.

Signed-off-by: Eric Sandeen <sandeen@sandeen.net>
Signed-off-by: Namjae Jeon <namjae.jeon@samsung.com>

2020-05-18 11:51:40 +09:00

balloc.c

exfat: Unify access to the boot sector

2020-04-22 20:14:05 +09:00

cache.c

exfat: add exfat cache

2020-03-05 21:00:40 -05:00

dir.c

exfat: add directory operations

2020-03-05 21:00:40 -05:00

exfat_fs.h

exfat: truncate atimes to 2s granularity