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

[Launchpad Bug Tracker]

This bug was fixed in the package glibc - 2.27-3ubuntu1.3

---------------
glibc (2.27-3ubuntu1.3) bionic; urgency=medium

  [ Balint Reczey ]
  * debian/gbp.conf: Add initial configuration
  * debian/control.in/main: Add Vcs-* pointing to Ubuntu packaging repository
  * arm64: Enable searching shared libraries in atomics/ on LSE HW
  * Ship arm64 variant with LSE support in libc6-lse (LP: #1885012)
  * Run tests of libc6-lse on HW supporting LSE
  * debian/patches/git-updates.diff: update from upstream stable branch
    - pthread_cond_broadcast: Fix waiters-after-spinning case
    - Fix SSe2-based memmove corrupting memory (CVE-2017-18269)
    - Fix strstr() performance regression on Haswell processors
    - Support Japanese new era "令和 (Reiwa)"
    - io: Remove copy_file_range emulation
    (LP: #1851263, #1858203, #1838327, #1797335, #1756209, #1853193)
  * XFAIL stdlib/tst-getrandom (LP: #1891403)
  * debian/testsuite-xfail-debian.mk: XFAIL new tst-support_descriptors

  [ Thadeu Lima de Souza Cascardo ]
  * tests: Make preadwritev2 invalid flags tests unsupported (LP: #1770480)

  [ Andreas Hasenack ]
  * branch-pthread_rwlock_trywrlock-hang-23844.patch:
    nptl: Fix pthread_rwlock_try*lock stalls (Bug 23844) (LP: #1864864)

 -- Balint Reczey <rbalint at ubuntu.com>  Wed, 02 Sep 2020 11:18:37 +0200

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

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-18269

-- 
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:
  Fix Released
Status in glibc package in Ubuntu:
  Fix Released
Status in glibc source package in Bionic:
  Fix Released

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