linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Anna Schumaker <Anna.Schumaker@netapp.com>
Cc: linux-nfs@vger.kernel.org, Trond.Myklebust@primarydata.com,
	bfields@fieldses.org, hch@infradead.org
Subject: Re: [PATCH v4 0/3] NFSv4.2: Add support for the COPY operation
Date: Sun, 1 May 2016 10:37:33 -0700	[thread overview]
Message-ID: <20160501173733.GA556@infradead.org> (raw)
In-Reply-To: <1461962533-26534-1-git-send-email-Anna.Schumaker@Netapp.com>

I might sound like a broken record, but I'd feel much happier if this
had extensive xfstests coverage.  Xfstests has over one hundred tests for
file clones, and many of them should be easily adapatable.

  parent reply	other threads:[~2016-05-01 17:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-29 20:42 [PATCH v4 0/3] NFSv4.2: Add support for the COPY operation Anna Schumaker
2016-04-29 20:42 ` [PATCH v4 1/3] NFS: Add nfs_commit_file() Anna Schumaker
2016-04-29 20:42 ` [PATCH v4 2/3] NFS: Add COPY nfs operation Anna Schumaker
2016-04-29 20:42 ` [PATCH v4 3/3] NFSD: Implement the COPY call Anna Schumaker
2016-04-29 20:42 ` [RFC v4 4/3] vfs_copy_range() test program Anna Schumaker
2016-05-01 17:37 ` Christoph Hellwig [this message]
2016-05-13 20:31   ` [PATCH v4 0/3] NFSv4.2: Add support for the COPY operation J. Bruce Fields
2016-05-13 20:58     ` Anna Schumaker
2016-07-29 18:59       ` J. Bruce Fields
2016-07-29 19:40         ` Anna Schumaker
2016-07-29 20:20           ` J. Bruce Fields
2016-07-29 20:44             ` Anna Schumaker
2016-07-29 21:21               ` J. Bruce Fields
2016-08-02 18:48                 ` J. Bruce Fields
2016-08-26 20:32             ` Anna Schumaker
2016-08-01 13:30         ` Christoph Hellwig

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=20160501173733.GA556@infradead.org \
    --to=hch@infradead.org \
    --cc=Anna.Schumaker@netapp.com \
    --cc=Trond.Myklebust@primarydata.com \
    --cc=bfields@fieldses.org \
    --cc=linux-nfs@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).