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

[Mathew Hodson]

This test was removed by upstream in recent versions.

** Changed in: glibc (Ubuntu)
       Status: Invalid => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1853193

Title:
  copy_file_range test fails with linux 5.3+ on bionic

Status in GLibC:
  Unknown
Status in glibc package in Ubuntu:
  Fix Released
Status in glibc source package in Bionic:
  In Progress

Bug description:
  [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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1853193/+subscriptions