[LTP] [PATCH v4] syscalls/copy_file_range: add/restructured tests

[Cyril Hrubis]

Hi!
> > > > 2) Glibc adds internal implementation of copy_file_range(), used as fallback
> > > > when kernel < 4.5 (which brought copy_file_range()) [1]. I guess there is no way
> > > > to use it explicitly :(.
> >
> > > Well we can always use filesystem that does not support the operation,
> > > so running the test for all filesystems should get the emulation covered
> > > for sure...
> > Oh, that's the way :).
> 
> Actually, there is no such thing as filesystem that does not support
> copy_file_range() because the kernel provides a fallback default implementation
> (in-kernel copy).

So the glibc fallback code is probably something that will end up being
used if someone wants to run application that uses this syscall on BSD
or other corner cases. I guess that we do not care that much about
testing the glibc fallback code then.

-- 
Cyril Hrubis
chrubis@suse.cz