From: "Zac Medico" <zmedico@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/portage:master commit in: src/
Date: Sat, 16 Dec 2017 00:38:30 +0000 (UTC) [thread overview]
Message-ID: <1513384698.dad9cce8a1e2360e8483e0f78e29e20bd5fdce49.zmedico@gentoo> (raw)
commit: dad9cce8a1e2360e8483e0f78e29e20bd5fdce49
Author: Zac Medico <zmedico <AT> gentoo <DOT> org>
AuthorDate: Sat Dec 16 00:37:40 2017 +0000
Commit: Zac Medico <zmedico <AT> gentoo <DOT> org>
CommitDate: Sat Dec 16 00:38:18 2017 +0000
URL: https://gitweb.gentoo.org/proj/portage.git/commit/?id=dad9cce8
file_copy: handle EOPNOTSUPP from copy_file_range (bug 641088)
NFS can set the errno to EOPNOTSUPP for copy_file_range.
Bug: https://bugs.gentoo.org/641088
src/portage_util_file_copy_reflink_linux.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/portage_util_file_copy_reflink_linux.c b/src/portage_util_file_copy_reflink_linux.c
index 81aae873a..352342c06 100644
--- a/src/portage_util_file_copy_reflink_linux.c
+++ b/src/portage_util_file_copy_reflink_linux.c
@@ -271,7 +271,7 @@ _reflink_linux_file_copy(PyObject *self, PyObject *args)
if (copyfunc_ret < 0) {
error = errno;
- if ((errno == EXDEV || errno == ENOSYS) &&
+ if ((errno == EXDEV || errno == ENOSYS || errno == EOPNOTSUPP) &&
copyfunc == cfr_wrapper) {
/* Use sendfile instead of copy_file_range for
* cross-device copies, or when the copy_file_range
next reply other threads:[~2017-12-16 0:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-16 0:38 Zac Medico [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-28 18:16 [gentoo-commits] proj/portage:master commit in: src/ Zac Medico
2023-08-02 15:50 Mike Gilbert
2023-06-07 7:29 Sam James
2021-12-12 1:14 Zac Medico
2020-12-25 0:28 Mike Gilbert
2017-12-15 21:17 Zac Medico
2017-10-27 18:50 Zac Medico
2017-05-14 18:08 Zac Medico
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1513384698.dad9cce8a1e2360e8483e0f78e29e20bd5fdce49.zmedico@gentoo \
--to=zmedico@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.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