From: robbieko <robbieko@synology.com>
To: linux-btrfs@vger.kernel.org
Cc: Robbie Ko <robbieko@synology.com>
Subject: [PATCH 0/5] Btrfs: incremental send, fix serval case for root and gen
Date: Wed, 12 Oct 2016 16:12:45 +0800 [thread overview]
Message-ID: <1476259970-1866-1-git-send-email-robbieko@synology.com> (raw)
From: Robbie Ko <robbieko@synology.com>
Patch for fix btrfs incremental send.
These patches base on v4.8.0-rc8
Robbie Ko (5):
Btrfs: incremental send, fix don't skip root inode in overwrite_ref
Btrfs: incremental send, add gen for is_waiting_for_rm when some
corner case
Btrfs: incremental send, add gen in waiting_dir_move for some corner
case
Btrfs: incremental send, add gen check in did_overwrite_ref
Btrfs: incremental send, add gen check if has waiting_dir_move in the
will_overwrite_ref
fs/btrfs/send.c | 50 ++++++++++++++++++++++++++++++++++++++++----------
1 file changed, 40 insertions(+), 10 deletions(-)
--
1.9.1
next reply other threads:[~2016-10-12 8:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 8:12 robbieko [this message]
2016-10-12 8:12 ` [PATCH 1/5] Btrfs: incremental send, fix don't skip root inode in overwrite_ref robbieko
2016-10-12 9:09 ` Filipe Manana
2016-10-12 8:12 ` [PATCH 2/5] Btrfs: incremental send, add gen for is_waiting_for_rm when some corner case robbieko
2016-10-12 9:11 ` Filipe Manana
2016-10-12 8:12 ` [PATCH 3/5] Btrfs: incremental send, add gen in waiting_dir_move for " robbieko
2016-10-12 9:13 ` Filipe Manana
2016-10-12 8:12 ` [PATCH 4/5] Btrfs: incremental send, add gen check in did_overwrite_ref robbieko
2016-10-12 9:14 ` Filipe Manana
2016-10-12 8:12 ` [PATCH 5/5] Btrfs: incremental send, add gen check if has waiting_dir_move in the will_overwrite_ref robbieko
2016-10-12 9:15 ` Filipe Manana
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=1476259970-1866-1-git-send-email-robbieko@synology.com \
--to=robbieko@synology.com \
--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 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.