From: Alexander Block <ablock84@googlemail.com>
To: Chris Mason <chris.mason@fusionio.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Btrfs send/receive fixes and PULL request
Date: Thu, 2 Aug 2012 11:55:18 +0200 [thread overview]
Message-ID: <CAB9VWqBk9CMHhJKq1rOeDXwDmoEVW7LiLCdbb+rbxmM--LOUKA@mail.gmail.com> (raw)
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(-)
next reply other threads:[~2012-08-02 9:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 9:55 Alexander Block [this message]
2012-08-02 10:09 ` Btrfs send/receive fixes and PULL request Alexander Block
2012-08-06 20:25 ` Chris Mason
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=CAB9VWqBk9CMHhJKq1rOeDXwDmoEVW7LiLCdbb+rbxmM--LOUKA@mail.gmail.com \
--to=ablock84@googlemail.com \
--cc=chris.mason@fusionio.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 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).