copy_file_range changed behavior on 5.3, which would cause such failures. LTP changes to accomodate that were committed on September 30th and October 29th, though.
Maybe this could be caused by the combination of linux 5.3, glibc 2.27 and whatever ltp version was used. Do we track the ltp commit id that was tested somehow? Cascardo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851653 Title: copy_file_range02 from ubuntu_ltp_syscalls failed on B-hwe-edge 5.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1851653/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
