Hello Chris,
You can find and pull a lot of fixes for btrfs send/receive in my git repo:
git://github.com/ablock84/linux-btrfs.git for-chris
These fixes are mostly the results of the reviews from Arne and Alex
that I got here on the list. I''m not posting the patches to the list
at the moment as they got quite a lot (23 patches). If anyone thinks I
should still post them, please tell me. The branch is based on current
master of Linus repo. As I already announced, I won''t have time to
work on btrfs starting from now.
Alex.
----------------------------------------------------------------
Alexander Block (23):
Btrfs: add rdev to get_inode_info in send/receive
Btrfs: fix cur_ino < parent_ino case for send/receive
Btrfs: add missing check for dir != tmp_dir to is_first_ref
Btrfs: remove unused code with #if 0
Btrfs: add correct parent to check_dirs when dir got moved
Btrfs: remove unused use_list from send/receive code
Btrfs: rename backref_ctx::found_in_send_root to found_itself
Btrfs: use kmalloc instead of stack for backref_ctx
Btrfs: use normal return path for root == send_root case
Btrfs: don''t break in the final loop of find_extent_clone
Btrfs: fix memory leak for name_cache in send/receive
Btrfs: fix use of radix_tree for name_cache in send/receive
Btrfs: make aux field of ulist 64 bit
Btrfs: update send_progress at correct places
Btrfs: add/fix comments/documentation for send/receive
Btrfs: code cleanups for send/receive
Btrfs: remove unused tmp_path from iterate_dir_item
Btrfs: free nce and nce_head on error in name_cache_insert
Btrfs: fix check for changed extent in is_extent_unchanged
Btrfs: use <= instead of < in is_extent_unchanged
Btrfs: pass root instead of parent_root to iterate_inode_ref
Btrfs: ignore non-FS inodes for send/receive
Btrfs: don''t treat top/root directory inode as deleted/reused
Dan Carpenter (1):
Btrfs: fix some endian bugs handling the root times
fs/btrfs/backref.c | 8 +-
fs/btrfs/ioctl.c | 2 +-
fs/btrfs/qgroup.c | 20 +-
fs/btrfs/root-tree.c | 4 +-
fs/btrfs/send.c | 851 ++++++++++++++++++++++++++----------------------
fs/btrfs/transaction.c | 2 +-
fs/btrfs/ulist.c | 7 +-
fs/btrfs/ulist.h | 9 +-
8 files changed, 483 insertions(+), 420 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs"
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, Aug 2, 2012 at 11:55 AM, Alexander Block <ablock84@googlemail.com> wrote:> Hello Chris, > > You can find and pull a lot of fixes for btrfs send/receive in my git repo: > > git://github.com/ablock84/linux-btrfs.git for-chris > > These fixes are mostly the results of the reviews from Arne and Alex > that I got here on the list. I''m not posting the patches to the list > at the moment as they got quite a lot (23 patches). If anyone thinks I > should still post them, please tell me. The branch is based on current > master of Linus repo. As I already announced, I won''t have time to > work on btrfs starting from now. > > Alex. > > ---------------------------------------------------------------- > Alexander Block (23): > Btrfs: add rdev to get_inode_info in send/receive > Btrfs: fix cur_ino < parent_ino case for send/receive > Btrfs: add missing check for dir != tmp_dir to is_first_ref > Btrfs: remove unused code with #if 0 > Btrfs: add correct parent to check_dirs when dir got moved > Btrfs: remove unused use_list from send/receive code > Btrfs: rename backref_ctx::found_in_send_root to found_itself > Btrfs: use kmalloc instead of stack for backref_ctx > Btrfs: use normal return path for root == send_root case > Btrfs: don''t break in the final loop of find_extent_clone > Btrfs: fix memory leak for name_cache in send/receive > Btrfs: fix use of radix_tree for name_cache in send/receive > Btrfs: make aux field of ulist 64 bit > Btrfs: update send_progress at correct places > Btrfs: add/fix comments/documentation for send/receive > Btrfs: code cleanups for send/receive > Btrfs: remove unused tmp_path from iterate_dir_item > Btrfs: free nce and nce_head on error in name_cache_insert > Btrfs: fix check for changed extent in is_extent_unchanged > Btrfs: use <= instead of < in is_extent_unchanged > Btrfs: pass root instead of parent_root to iterate_inode_ref > Btrfs: ignore non-FS inodes for send/receive > Btrfs: don''t treat top/root directory inode as deleted/reused > > Dan Carpenter (1): > Btrfs: fix some endian bugs handling the root times > > fs/btrfs/backref.c | 8 +- > fs/btrfs/ioctl.c | 2 +- > fs/btrfs/qgroup.c | 20 +- > fs/btrfs/root-tree.c | 4 +- > fs/btrfs/send.c | 851 ++++++++++++++++++++++++++---------------------- > fs/btrfs/transaction.c | 2 +- > fs/btrfs/ulist.c | 7 +- > fs/btrfs/ulist.h | 9 +- > 8 files changed, 483 insertions(+), 420 deletions(-)I forgot to write where to find the btrfs-progs fixes: git://github.com/ablock84/btrfs-progs.git for-chris -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, Aug 02, 2012 at 03:55:18AM -0600, Alexander Block wrote:> Hello Chris, > > You can find and pull a lot of fixes for btrfs send/receive in my git repo: > > git://github.com/ablock84/linux-btrfs.git for-chris > > These fixes are mostly the results of the reviews from Arne and Alex > that I got here on the list. I''m not posting the patches to the list > at the moment as they got quite a lot (23 patches). If anyone thinks I > should still post them, please tell me. The branch is based on current > master of Linus repo. As I already announced, I won''t have time to > work on btrfs starting from now.Great, I''m pulling these in now. For any future pulls, please do them against my tree instead of Linus'' git. That way we can play with the latest btrfs code on top of the current stable kernel, instead of the devel kernel. I''m rebasing this one against my current tree. -chris -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html