kernel/git/stable/linux.git/fs/btrfs/send.c, branch linux-3.8.y

Btrfs: fix memory leak in name_cache_insert()

2013-01-14T18:52:30+00:00

We should free name_cache_entry before returning from the error handling code. Signed-off-by: Tsutomu Itoh

Btrfs: rename root_times_lock to root_item_lock

2012-12-17T01:46:21+00:00

Originally root_times_lock was introduced as part of send/receive code however newly developed patch to label the subvol reused the same lock, so renaming it for a meaningful name. Signed-off-by: Anand Jain Signed-off-by: Chris Mason

Btrfs: Send: preserve ownership (uid and gid) also for symlinks.

2012-10-25T19:47:31+00:00

This patch also requires a change in the user-space part of "receive". We need to use "lchown" instead of "chown". We will do this in the following patch. Signed-off-by: Alex Lyakas if (S_ISREG(sctx->cur_inode_mode)) {

Btrfs: send correct rdev and mode in btrfs-send

2012-10-25T19:45:25+00:00

When sending a device file, the stream was missing the mode. Also the rdev was encoded wrongly. Signed-off-by: Arne Jansen

Btrfs: extended inode refs support for send mechanism

2012-10-25T19:45:16+00:00

This adds support for the new extended inode refs to btrfs send. Signed-off-by: Jan Schmidt

Btrfs: write_buf is now callable outside send.c

2012-10-04T13:39:55+00:00

Developing service cmds needs it. Signed-off-by: Anand Jain

Btrfs: fix a bug in parsing return value in logical resolve

2012-10-01T19:19:18+00:00

In logical resolve, we parse extent_from_logical()'s 'ret' as a kind of flag. It is possible to lose our errors because (-EXXXX & BTRFS_EXTENT_FLAG_TREE_BLOCK) is true. I'm not sure if it is on purpose, it just looks too hacky if it is. I'd rather use a real flag and a 'ret' to catch errors. Acked-by: Jan Schmidt Signed-off-by: Liu Bo

Btrfs: fix gcc warnings for 32bit compiles

2012-10-01T19:19:01+00:00

Signed-off-by: Jan Schmidt Signed-off-by: Chris Mason

Btrfs: fix btrfs send for inline items and compression

2012-10-01T19:19:00+00:00

The btrfs send code was assuming the offset of the file item into the extent translated to bytes on disk. If we're compressed, this isn't true, and so it was off into extents owned by other files. It was also improperly handling inline extents. This solves a crash where we may have gone past the end of the file extent item by not testing early enough for an inline extent. It also solves problems where we have a whole between the end of the inline item and the start of the full extent. Signed-off-by: Chris Mason

Btrfs: don't treat top/root directory inode as deleted/reused

2012-10-01T19:19:00+00:00

We can't do the deleted/reused logic for top/root inodes as it would create a stream that tries to delete and recreate the root dir. Reported-by: Alex Lyakas Signed-off-by: Alexander Block