When building in a RHEL 7 container on a RHEL 8 host, the current configure check will detect a working SYS_copy_file_range() syscall. Later when the resulting smbd binary is run in a RHEL 7 container on a RHEl 7 (vs 8 on the build host) host, SYS_copy_file_range() will fail with EOPNOTSUPP. We have to catch this in vfs_default and fallback to userspace copy in that case.
This bug was referenced in samba master: c25f72f401842a18cab1db2bab89deec78274d93 1641e6c528e027dbfff96a834b94a8654a03a168
Created attachment 16736 [details] Patch for 4.15 cherry-picked from master
Pushed to autobuild-v4-15-test.
This bug was referenced in samba v4-15-test: 681675b68c5dbbb4089067b2db9f11d69b2d085c 7c8ba49b2e9d963deccdea5bc16a8f43e1ce9fcf
Closing out bug report. Thanks!
This bug was referenced in samba v4-15-stable (Release samba-4.15.0rc3): 681675b68c5dbbb4089067b2db9f11d69b2d085c 7c8ba49b2e9d963deccdea5bc16a8f43e1ce9fcf