From: Mike Marshall <hubcap@omnibond.com>
To: linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Mike Marshall <hubcapsc@gmail.com>,
Mike Marshall <hubcap@omnibond.com>
Subject: "do_copy_range:: Invalid argument"
Date: Fri, 11 Dec 2020 11:26:28 -0500 [thread overview]
Message-ID: <CAOg9mSSCsPPYpHGAWVHoY5bO8DozzFNWXTi39XBc+GhDmWcRTA@mail.gmail.com> (raw)
Greetings everyone...
Omnibond has sent me off doing some testing chores lately.
I made no Orangefs patches for 5.9 or 5.10 and none were sent,
but I thought I should at least run through xfstests.
There are tests that fail on 5.10-rc6 that didn't fail
on 5.8-rc7, and I've done enough looking to see that the
failure reasons all seem related.
I will, of course, keep looking to try and understand these
failures. Bisection might lead me somewhere. In case the
notes I've taken so far trigger any of y'all to give me
any (constructive :-) ) suggestions, I've included them below.
-Mike
---------------------------------------------------------------------
generic/075
58rc7: ? (check.log says it ran, results file missing)
510rc6: failed, "do_copy_range:: Invalid argument"
read the tests/generic/075 commit message for "detect
preallocation support for fsx tests"
generic/091
58rc7: passed, but skipped fallocate parts "filesystem does not support"
510rc6: failed, "do_copy_range:: Invalid argument"
generic/112
58rc7: ? (check.log says it ran, results file missing)
510rc6: failed, "do_copy_range:: Invalid argument"
generic/127
58rc7: ? (check.log says it ran, results file missing)
510rc6: failed, "do_copy_range:: Invalid argument"
generic/249
58rc7: passed
510rc6: failed, "sendfile: Invalid argument"
man 2 sendfile -> "SEE ALSO copy_file_range(2)"
generic/263
58rc7: passed
510rc6: failed, "do_copy_range:: Invalid argument"
generic/434
58rc7: failed "copy_range: Bad file descriptor"
510rc6: not run "xfs_io copy_range failed (old kernel/wrong fs/bad args?)"
next reply other threads:[~2020-12-11 17:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 16:26 Mike Marshall [this message]
2020-12-14 3:05 ` "do_copy_range:: Invalid argument" Dave Chinner
2020-12-14 4:07 ` Matthew Wilcox
2020-12-15 20:20 ` Mike Marshall
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=CAOg9mSSCsPPYpHGAWVHoY5bO8DozzFNWXTi39XBc+GhDmWcRTA@mail.gmail.com \
--to=hubcap@omnibond.com \
--cc=hubcapsc@gmail.com \
--cc=linux-fsdevel@vger.kernel.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 NNTP newsgroup(s).