Re: New glibc-testfail io/tst-copy_file_range with kernel-next.

[Stefan Liebler <stli at linux dot ibm dot com>]

On 6/26/19 4:18 PM, Florian Weimer wrote:
> * Stefan Liebler:
>
> > as information, I had the chance to run the glibc-testsuite on a
> > kernel-next from today on s390x and recognized a new failing test:
> > io/tst-copy_file_range
>
> Thanks for looking at this and summarizing the changes.
>
> There's been a previous thread here:
>
>    <https://sourceware.org/ml/libc-alpha/2019-06/msg00039.html>
>
> I can back out the emulation, as discussed, then there wouldn't be
> anything left to test in theory (although I think our tests caught one
> or two bugs in XFS backports downstream, that as before fstests covered
> copy_file_range).
>
> It's not easy for me to test linux-next, but I can try to tweak the test
> so that it copes with the different error codes.
>
> The cross-device test we should just drop.
>
> Thanks,
> Florian

Just for reference:
here are the links to Florians patch / commit which removes part of the 
tests. Now the test is passing on the mentioned kernel-next:

"[PATCH] io: Remove copy_file_range emulation"
https://www.sourceware.org/ml/libc-alpha/2019-06/msg00873.html

"io: Remove copy_file_range emulation [BZ #24744]"
https://sourceware.org/git/?p=glibc.git;a=commit;h=5a659ccc0ec217ab02a4c273a1f6d346a359560a

Thanks,
Stefan