ZFS 2.0 (tip, on commit 71ae6a9d232de59534e4337efb0dc85c7d6906bd)
SPL Version
as above
Describe the problem you're observing
Running xfs test 075 I'm seeing a regression just on the 5.10-rc2 kernel (and not on the 5.9 stable kernel) with ZFS. The failure is in copy_file_range returning -EINVAL with the 5.10-rc2 kernel where as in 5.9 it works fine.
The test exercises "pre-allocate file space, exercising unwritten extents". The same failure occurs also for the generic xfs test 112 that is a variation of test 075 but also uses AIO system calls.
Just a side note, I back-ported the ZFS 5.10/5.9 compat changes to an earlier 0.8.4 ZFS and I see the same issue, so I'm not sure if this a 5.10-rc2 issue or a ZFS compat issue or a combo of both.
Describe how to reproduce the problem
Run the current xfs tests on ZFS, test 075. I've distilled this down to a reproducer script:
System information
Describe the problem you're observing
Running xfs test 075 I'm seeing a regression just on the 5.10-rc2 kernel (and not on the 5.9 stable kernel) with ZFS. The failure is in copy_file_range returning -EINVAL with the 5.10-rc2 kernel where as in 5.9 it works fine.
The test exercises "pre-allocate file space, exercising unwritten extents". The same failure occurs also for the generic xfs test 112 that is a variation of test 075 but also uses AIO system calls.
Just a side note, I back-ported the ZFS 5.10/5.9 compat changes to an earlier 0.8.4 ZFS and I see the same issue, so I'm not sure if this a 5.10-rc2 issue or a ZFS compat issue or a combo of both.
Describe how to reproduce the problem
Run the current xfs tests on ZFS, test 075. I've distilled this down to a reproducer script:
With 5.10-rc2, the failure is as follows:
Where as with 5.9 it runs successfully, there are multiple copy_file_range calls that work fine.