From: David Sterba <dsterba@suse.cz>
To: dsterba@suse.cz, fdmanana@kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v4 0/3] Add full support for cloning inline extents
Date: Fri, 6 Mar 2020 21:19:52 +0100 [thread overview]
Message-ID: <20200306201952.GL2902@twin.jikos.cz> (raw)
In-Reply-To: <20200228134947.GJ2902@twin.jikos.cz>
On Fri, Feb 28, 2020 at 02:49:47PM +0100, David Sterba wrote:
> On Fri, Feb 28, 2020 at 01:04:16PM +0000, fdmanana@kernel.org wrote:
> > From: Filipe Manana <fdmanana@suse.com>
> >
> > This patchset adds support for currently unsupported cases of reflink
> > operations that cover a file range that has inline extents, more details
> > on why/how in patch 3/3.
> >
> > It also starts by moving all the reflink code out of ioctl.c into a new
> > file named reflink.c (like xfs does) since this code is quite significant
> > in size and has grown over the years.
> >
> > V4: Updated patch 3 to fix a deadlock due to allocating space while holding
> > a transaction open. No changes to the first two patches.
>
> V4 replaced in for-next, thanks.
Moved to misc-next.
prev parent reply other threads:[~2020-03-06 20:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 13:04 [PATCH v4 0/3] Add full support for cloning inline extents fdmanana
2020-02-28 13:04 ` [PATCH v4 1/3] Btrfs: move all reflink implementation code into its own file fdmanana
2020-02-28 13:04 ` [PATCH v4 2/3] Btrfs: simplify inline extent handling when doing reflinks fdmanana
2020-02-28 13:04 ` [PATCH v4 3/3] Btrfs: implement full reflink support for inline extents fdmanana
2020-02-28 13:49 ` [PATCH v4 0/3] Add full support for cloning " David Sterba
2020-03-06 20:19 ` David Sterba [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=20200306201952.GL2902@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=fdmanana@kernel.org \
--cc=linux-btrfs@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