[Bug 1853193] [NEW] copy_file_range test fails with linux 5.3+ on bionic

Launchpad Bug Tracker 1853193 at bugs.launchpad.net
Mon Jun 29 20:34:21 UTC 2020


You have been subscribed to a public bug by Thadeu Lima de Souza Cascardo (cascardo):

[Impact]
When tested against newer versions of linux, glibc tests will fail as it makes some assumptions about supportead features on the kernel.

[Fix]
Do not run the test that checks that copy_file_range will fail with EXDEV when done across devices.

[Test case]
Build glibc and run its tests on linux 5.3.

[Regression potential]
The same test is being ignored right now, we risk ignoring a failure on an older version of linux, like 4.15. However, that could happen because the feature is backported to said kernel. And we are currently ignoring the failure anyway.

===================================

copy_file_range on linux 5.3 now works across devices, so EXDEV is not
returned anymore on those cases. glibc, however, tests that is the case
and its autopkgtest fails, then, when running on linux 5.3.

glibc 2.30 does not fail in that case anymore, so eoan glibc works fine
on linux 5.3. However, the change on glibc 2.30 was to remove its
userspace emulation entirely, and require users to fallback on their
own.

https://sourceware.org/bugzilla/show_bug.cgi?id=24744

Linux commit 5dae222a5ff0c269730393018a5539cc970a4726.

** Affects: glibc (Ubuntu)
     Importance: Undecided
         Status: Invalid

** Affects: glibc (Ubuntu Bionic)
     Importance: Undecided
     Assignee: Thadeu Lima de Souza Cascardo (cascardo)
         Status: In Progress

-- 
copy_file_range test fails with linux 5.3+ on bionic
https://bugs.launchpad.net/bugs/1853193
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.



More information about the Ubuntu-sponsors mailing list