public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/26338] io/tst-copy_file_range fails on RHEL 7.8 hosts
Date: Wed, 05 Aug 2020 14:25:01 +0000	[thread overview]
Message-ID: <bug-26338-131-3km5KOFrG9@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26338-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=26338

--- Comment #7 from Florian Weimer <fweimer at redhat dot com> ---
Most file systems I looked at have something like this:

static ssize_t nfs4_copy_file_range(struct file *file_in, loff_t pos_in,
                                    struct file *file_out, loff_t pos_out,
                                    size_t count, unsigned int flags)
{
        ssize_t ret;

        ret = __nfs4_copy_file_range(file_in, pos_in, file_out, pos_out, count,
                                     flags);
        if (ret == -EOPNOTSUPP || ret == -EXDEV)
                ret = generic_copy_file_range(file_in, pos_in, file_out,
                                              pos_out, count, flags);
        return ret;
}

This masks the EOPNOTSUPP error from the native copy_file_range implementation
and calls generic_copy_file_range even if do_copy_file_range does not.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2020-08-05 14:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-05 11:47 [Bug build/26338] New: " romain.geissler at amadeus dot com
2020-08-05 12:42 ` [Bug build/26338] " adhemerval.zanella at linaro dot org
2020-08-05 13:24 ` carlos at redhat dot com
2020-08-05 13:38 ` fweimer at redhat dot com
2020-08-05 14:01 ` adhemerval.zanella at linaro dot org
2020-08-05 14:08 ` fweimer at redhat dot com
2020-08-05 14:20 ` adhemerval.zanella at linaro dot org
2020-08-05 14:25 ` fweimer at redhat dot com [this message]
2020-08-05 14:28 ` adhemerval.zanella at linaro dot org
2020-08-07  9:56 ` romain.geissler at amadeus dot com
2020-08-07 10:06 ` fweimer at redhat dot com
2020-08-07 10:07 ` [Bug build/26338] io/tst-copy_file_range may incorrectly detect availability of copy_file_range file system support fweimer at redhat dot com

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=bug-26338-131-3km5KOFrG9@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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).