bug-coreutils@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: "Pádraig Brady" <P@draigBrady.com>
To: Paul Eggert <eggert@cs.ucla.edu>, Sam James <sam@gentoo.org>
Cc: 63850@debbugs.gnu.org, floppym@gentoo.org
Subject: bug#63850: cp fails for files > 2 GB if copy offload is unsupported
Date: Tue, 6 Jun 2023 10:53:50 +0100	[thread overview]
Message-ID: <2cab32d9-0235-f1a4-752c-2480c5862456@draigBrady.com> (raw)
In-Reply-To: <646de69d-a23e-8f59-167f-6e7476abc484@cs.ucla.edu>

On 06/06/2023 06:48, Paul Eggert wrote:
> On 2023-06-05 22:26, Sam James wrote:
>> It's just that linux-headers is
>> a special case
> 
> Indeed it is. And apparently glibc avoids the copy_file_range bugs by
> never, ever using copy_file_range internally - which explains why glibc
> hasn't run into this backward compatibility issue. Presumably once glibc
> starts assuming kernel 5.3 or later, it can start using copy_file_range
> internally.

Yes, glibc has the --enable-kernel configure option
to allow setting the compatibility range independently
from the build host (kernel headers).
In my experience a distro needs to support quite a range of kernel versions
mainly due to certain hardware platforms being tied to older kernels.

> Anyway, thanks for explaining. I installed the patch I mentioned into
> Gnulib and have updated coreutils accordingly on Savannah master. Please
> give it a try.

Thanks for making the change Paul.

Pádraig




  reply	other threads:[~2023-06-06  9:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-02 15:44 bug#63850: cp fails for files > 2 GB if copy offload is unsupported Sam James
2023-06-02 16:31 ` Pádraig Brady
2023-06-03  1:02   ` Mike Gilbert
2023-06-03  5:25     ` Pádraig Brady
2023-06-03  6:05   ` Paul Eggert
2023-06-03 13:54     ` Mike Gilbert
2023-06-03 17:12       ` Arsen Arsenović via GNU coreutils Bug Reports
2023-06-06  4:48       ` Paul Eggert
2023-06-06  5:07         ` Paul Eggert
2023-06-06  5:09         ` Sam James
2023-06-06  5:26           ` Sam James
2023-06-06  5:48             ` Paul Eggert
2023-06-06  9:53               ` Pádraig Brady [this message]
2023-06-06 10:02               ` Sam James
2023-06-06 10:27                 ` Pádraig Brady
2023-06-07 19:13                 ` Paul Eggert
2023-06-07 19:21                   ` Sam James
2023-06-07 19:44                     ` Paul Eggert
2023-06-08 11:28                       ` Arsen Arsenović via GNU coreutils Bug Reports
2023-06-08 17:44                         ` Paul Eggert
2023-06-03 18:39     ` Pádraig Brady

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.gnu.org/mailman/listinfo/bug-coreutils

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2cab32d9-0235-f1a4-752c-2480c5862456@draigBrady.com \
    --to=p@draigbrady.com \
    --cc=63850@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=floppym@gentoo.org \
    --cc=sam@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).