From: Sam James <sam@gentoo.org>
To: 60455@debbugs.gnu.org
Subject: bug#60455: Missing fallback if copy_file_range returns ENOENT?
Date: Sat, 31 Dec 2022 17:00:48 +0000 [thread overview]
Message-ID: <C907B90E-B66B-468C-8C71-46FD348AB7EF@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 506 bytes --]
Hi folks,
Originally reported in Gentoo at https://bugs.gentoo.org/885793.
Frank Limpert reported that when copying large files across CIFS shares,
cp may abort because copy_file_range returns ENOENT sometimes.
This sounds like a suspicious kernel bug if CIFS interactions are sometimes
spuriously giving ENOENT, but I'm wondering if coreutils needs to do
anything to handle this as well.
strace output from his cp invocation: https://bugs.gentoo.org/attachment.cgi?id=842497
Best,
sam
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 358 bytes --]
next reply other threads:[~2022-12-31 17:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-31 17:00 Sam James [this message]
2022-12-31 18:51 ` bug#60455: Missing fallback if copy_file_range returns ENOENT? Pádraig Brady
2023-01-07 7:34 ` Sam James
2023-01-07 16:25 ` Pádraig Brady
2023-01-08 0:51 ` Sam James
2023-01-08 13:45 ` 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=C907B90E-B66B-468C-8C71-46FD348AB7EF@gentoo.org \
--to=sam@gentoo.org \
--cc=60455@debbugs.gnu.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).