From: Christoph Hellwig <hch@infradead.org>
To: Anna Schumaker <Anna.Schumaker@netapp.com>
Cc: fstests@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: sys_copy_file_range tests
Date: Fri, 4 Dec 2015 00:28:43 -0800 [thread overview]
Message-ID: <20151204082843.GA23145@infradead.org> (raw)
In-Reply-To: <5660A974.3010200@Netapp.com>
On Thu, Dec 03, 2015 at 03:43:32PM -0500, Anna Schumaker wrote:
> Sadly, I don't have very good tests and I was mostly using the example
> program from the man page under various filesystems and setups. At LPC,
> Darrick made it sound like he was going to work on adding
> vfs_copy_file_range() tests to xfstests but that probably turned into
> the reflink/dedupe ioctl tests.
>
> I can try to find time to write something for xfstests if that would
> be useful!
Yes, Darrick wrote a lot of clone tests. Some of the aren't applicable
to a pure copy, but I looking over them anc checking what should apply
would be very useful!
prev parent reply other threads:[~2015-12-04 8:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 18:10 sys_copy_file_range tests Christoph Hellwig
2015-12-03 20:43 ` Anna Schumaker
2015-12-03 20:43 ` Anna Schumaker
2015-12-04 8:28 ` Christoph Hellwig [this message]
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=20151204082843.GA23145@infradead.org \
--to=hch@infradead.org \
--cc=Anna.Schumaker@netapp.com \
--cc=fstests@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.