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

Thu Jul 2 15:54:49 UTC 2020

Launchpad has imported 6 comments from the remote bug at
https://sourceware.org/bugzilla/show_bug.cgi?id=24744.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2019-06-28T07:38:49+00:00 Florian Weimer wrote:

The kernel is evolving this interface rapidly, and our emulation is no
longer faithful: Among other things, we do not detect overlapping copies
(which is quite hard outside the kernel).  The kernel also plans to
support cross-device copies.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1853193/comments/0

------------------------------------------------------------------------
On 2019-06-28T08:10:57+00:00 Cvs-commit wrote:

The master branch has been updated by Florian Weimer
<fw at sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=5a659ccc0ec217ab02a4c273a1f6d346a359560a

commit 5a659ccc0ec217ab02a4c273a1f6d346a359560a
Author: Florian Weimer <fweimer at redhat.com>
Date:   Fri Jun 28 09:39:21 2019 +0200

    io: Remove copy_file_range emulation [BZ #24744]

    The kernel is evolving this interface (e.g., removal of the
    restriction on cross-device copies), and keeping up with that
    is difficult.  Applications which need the function should
    run kernels which support the system call instead of relying on
    the imperfect glibc emulation.

    Reviewed-by: Adhemerval Zanella <adhemerval.zanella at linaro.org>

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1853193/comments/1

------------------------------------------------------------------------
On 2019-06-28T08:11:21+00:00 Florian Weimer wrote:

Fixed in glibc 2.30.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1853193/comments/2

------------------------------------------------------------------------
On 2019-07-09T08:24:03+00:00 Cvs-commit wrote:

The release/2.29/master branch has been updated by Florian Weimer
<fw at sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=da347f4aa3a67e018f19e51a7ece6add87dba5cf

commit da347f4aa3a67e018f19e51a7ece6add87dba5cf
Author: Florian Weimer <fweimer at redhat.com>
Date:   Fri Jun 28 09:39:21 2019 +0200

    io: Remove copy_file_range emulation [BZ #24744]

    The kernel is evolving this interface (e.g., removal of the
    restriction on cross-device copies), and keeping up with that
    is difficult.  Applications which need the function should
    run kernels which support the system call instead of relying on
    the imperfect glibc emulation.

    Reviewed-by: Adhemerval Zanella <adhemerval.zanella at linaro.org>
    (cherry picked from commit 5a659ccc0ec217ab02a4c273a1f6d346a359560a)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1853193/comments/3

------------------------------------------------------------------------
On 2019-07-09T08:47:01+00:00 Cvs-commit wrote:

The release/2.27/master branch has been updated by Florian Weimer
<fw at sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=949da7f2fd0bc0f8dca91892e5c926504a7d11c2

commit 949da7f2fd0bc0f8dca91892e5c926504a7d11c2
Author: Florian Weimer <fweimer at redhat.com>
Date:   Fri Jun 28 09:39:21 2019 +0200

    io: Remove copy_file_range emulation [BZ #24744]

    The kernel is evolving this interface (e.g., removal of the
    restriction on cross-device copies), and keeping up with that
    is difficult.  Applications which need the function should
    run kernels which support the system call instead of relying on
    the imperfect glibc emulation.

    Reviewed-by: Adhemerval Zanella <adhemerval.zanella at linaro.org>
    (cherry picked from commit 5a659ccc0ec217ab02a4c273a1f6d346a359560a)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1853193/comments/4

------------------------------------------------------------------------
On 2019-07-09T09:25:02+00:00 Cvs-commit wrote:

The release/2.28/master branch has been updated by Florian Weimer
<fw at sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=5f7fa9ac30048bcc1d883cf52a544ea182882ee9

commit 5f7fa9ac30048bcc1d883cf52a544ea182882ee9
Author: Florian Weimer <fweimer at redhat.com>
Date:   Fri Jun 28 09:39:21 2019 +0200

    io: Remove copy_file_range emulation [BZ #24744]

    The kernel is evolving this interface (e.g., removal of the
    restriction on cross-device copies), and keeping up with that
    is difficult.  Applications which need the function should
    run kernels which support the system call instead of relying on
    the imperfect glibc emulation.

    Reviewed-by: Adhemerval Zanella <adhemerval.zanella at linaro.org>
    (cherry picked from commit 5a659ccc0ec217ab02a4c273a1f6d346a359560a)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1853193/comments/5

** Changed in: glibc
       Status: Unknown => Fix Released

** Changed in: glibc
   Importance: Unknown => Medium

-- 
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:
  Fix Released
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