linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Eric Ren <zren@suse.com>
Cc: mfasheh@versity.com, jlbec@evilplan.org,
	linux-fsdevel@vger.kernel.org, ocfs2-devel@oss.oracle.com
Subject: Re: [PATCH 0/6] ocfs2: wire up {clone,copy,dedupe}_range
Date: Fri, 11 Nov 2016 07:05:01 -0800	[thread overview]
Message-ID: <20161111150501.GE16807@birch.djwong.org> (raw)
In-Reply-To: <4d01515b-7511-22f7-4c71-ae76eab0ec47@suse.com>

On Fri, Nov 11, 2016 at 11:15:57AM +0800, Eric Ren wrote:
> Hi,
> 
> On 11/10/2016 06:51 AM, Darrick J. Wong wrote:
> >Hi all,
> >
> >These patches wire up the existing ocfs2 reflinking capabilities to
> >the new(ish) VFS {copy,clone,dedupe}_range interface.  The first few
> >patches clean up some minor bugs that I found; the last kernel patch
> >contains the new code.
> >
> >A few minor fixes to xfstests are needed to make more of the tests
> >run.  I'll tack that patch on the end.
> 
> FYI, reflink testcases from ocfs2-test both on single and multiple node(s)
> all passed with your patches. At least, it shows that no obvious regression issue
> is observed so far ;-)

Heh, good. :)

The v2 patch contains some fixes for a few things I thought of last night
that don't have xfstests yet.

I /think/ the locking is ok, but that could use some review. :)

--D

> 
> Eric
> >
> >--D
> >
> >[1] https://github.com/djwong/linux/tree/ocfs2-vfs-reflink
> >--
> >To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> >the body of a message to majordomo@vger.kernel.org
> >More majordomo info at  http://vger.kernel.org/majordomo-info.html
> >
> 

      reply	other threads:[~2016-11-11 15:05 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-09 22:51 [PATCH 0/6] ocfs2: wire up {clone,copy,dedupe}_range Darrick J. Wong
2016-11-09 22:51 ` [PATCH 1/6] ocfs2: convert inode refcount test to a helper Darrick J. Wong
2016-11-10  2:14   ` Eric Ren
2016-11-10 17:51     ` Darrick J. Wong
2016-11-10 17:52   ` [PATCH v2 " Darrick J. Wong
2016-11-09 22:51 ` [PATCH 2/6] ocfs2: add newlines to some error messages Darrick J. Wong
2016-11-09 22:51 ` [PATCH 3/6] ocfs2: prohibit refcounted swapfiles Darrick J. Wong
2016-11-09 22:51 ` [PATCH 4/6] ocfs2: budget for extent tree splits when adding refcount flag Darrick J. Wong
2016-11-10  9:20   ` [Ocfs2-devel] " Darwin
2016-11-10 17:11     ` Darrick J. Wong
2016-11-11  3:00       ` Darwin
2016-11-09 22:51 ` [PATCH 5/6] ocfs2: don't eat io errors during _dio_end_io_write Darrick J. Wong
2016-11-09 22:51 ` [PATCH 6/6] ocfs2: implement the VFS clone_range, copy_range, and dedupe_range features Darrick J. Wong
2016-11-11  5:49   ` [Ocfs2-devel] " Eric Ren
2016-11-11  6:20     ` Darrick J. Wong
2016-11-11  6:45       ` Eric Ren
2016-11-11  9:01         ` Darrick J. Wong
2016-11-11 14:54   ` [PATCH v2 " Darrick J. Wong
2016-11-09 23:00 ` [PATCH 7/6] xfstests: fix some minor problems testing ocfs2 Darrick J. Wong
2016-11-11  3:15 ` [PATCH 0/6] ocfs2: wire up {clone,copy,dedupe}_range Eric Ren
2016-11-11 15:05   ` Darrick J. Wong [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=20161111150501.GE16807@birch.djwong.org \
    --to=darrick.wong@oracle.com \
    --cc=jlbec@evilplan.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=mfasheh@versity.com \
    --cc=ocfs2-devel@oss.oracle.com \
    --cc=zren@suse.com \
    /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).