linux-stable.git/fs/btrfs/compression.c, branch linux-3.3.y

Btrfs: check return value of lookup_extent_mapping() correctly

2012-02-16T16:23:17+00:00

This patch corrects error checking of lookup_extent_mapping().

Signed-off-by: Tsutomu Itoh

btrfs: separate superblock items out of fs_info

2011-11-06T08:04:01+00:00

fs_info has now ~9kb, more than fits into one page. This will cause
mount failure when memory is too fragmented. Top space consumers are
super block structures super_copy and super_for_commit, ~2.8kb each.
Allocate them dynamically. fs_info will be ~3.5kb. (measured on x86_64)

Add a wrapper for freeing fs_info and all of it's dynamically allocated
members.

Signed-off-by: David Sterba

Btrfs: check the nodatasum flag when writing compressed files

2011-08-01T18:30:46+00:00

If mounting with nodatasum option, we won't csum file data for
general write or direct-io write, and this rule should also be
applied when writing compressed files.

Signed-off-by: Li Zefan 
Signed-off-by: Chris Mason

Merge branch 'cleanups' of git://repo.or.cz/linux-2.6/btrfs-unstable into inode_numbers

2011-05-22T16:33:42+00:00

Conflicts:
	fs/btrfs/extent-tree.c
	fs/btrfs/free-space-cache.c
	fs/btrfs/inode.c
	fs/btrfs/tree-log.c

Signed-off-by: Chris Mason

btrfs: rename variables clashing with global function names

2011-05-02T11:57:19+00:00

reported by gcc -Wshadow:
page_index, page_offset, new_inode, dev_name

Signed-off-by: David Sterba

Btrfs: Always use 64bit inode number

2011-04-25T08:46:09+00:00

There's a potential problem in 32bit system when we exhaust 32bit inode
numbers and start to allocate big inode numbers, because btrfs uses
inode->i_ino in many places.

So here we always use BTRFS_I(inode)->location.objectid, which is an
u64 variable.

There are 2 exceptions that BTRFS_I(inode)->location.objectid !=
inode->i_ino: the btree inode (0 vs 1) and empty subvol dirs (256 vs 2),
and inode->i_ino will be used in those cases.

Another reason to make this change is I'm going to use a special inode
to save free ino cache, and the inode number must be > (u64)-256.

Signed-off-by: Li Zefan

Btrfs: check return value of btrfs_alloc_path()

2011-03-28T09:37:54+00:00

Adding the check on the return value of btrfs_alloc_path() to several places.
And, some of callers are modified by this change.

Signed-off-by: Tsutomu Itoh 
Signed-off-by: Chris Mason

Btrfs: fix uncheck memory allocations

2011-03-28T09:37:49+00:00

To make Btrfs code more robust, several return value checks where memory
allocation can fail are introduced. I use BUG_ON where I don't know how
to handle the error properly, which increases the number of using the
notorious BUG_ON, though.

Signed-off-by: Yoshinori Sano 
Signed-off-by: Chris Mason

btrfs: Drop __exit attribute on btrfs_exit_compress

2011-02-06T12:19:19+00:00

As this function is called in some error paths while not
removing the module, the __exit attribute prevents the kernel
image from linking when btrfs is compiled in statically.

Signed-off-by: Alexey Charkov 
Signed-off-by: Chris Mason

btrfs: fix uncheck memory allocation in btrfs_submit_compressed_read

2011-01-28T21:40:36+00:00

btrfs_submit_compressed_read() is lack of memory allocation checks and
corresponding error route.

After this fix, if it comes to "no memory" case, errno will be returned
to userland step by step, and tell users this operation cannot go on.

Signed-off-by: Liu Bo 
Signed-off-by: Chris Mason