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

[Thadeu Lima de Souza Cascardo]

Public bug reported:

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
         Status: New

** Also affects: glibc (Ubuntu Bionic)
   Importance: Undecided
       Status: New

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

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to glibc in Ubuntu.
https://bugs.launchpad.net/bugs/1853193

Title:
  copy_file_range test fails with linux 5.3+ on bionic

Status in glibc package in Ubuntu:
  Invalid
Status in glibc source package in Bionic:
  New

Bug description:
  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/ubuntu/+source/glibc/+bug/1853193/+subscriptions