linux-toradex.git/fs/btrfs/backref.c, branch v3.7-rc7

Merge branch 'for-chris-fixed' of git://git.jan-o-sch.net/btrfs-unstable

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

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

Fix a sign bug causing invalid memory access in the ino_paths ioctl.

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

To see the problem, create many hardlinks to the same file (120 should do it),
then look up paths by inode with:

  ls -i
  btrfs inspect inode-resolve -v $ino /mnt/btrfs

I noticed the memory layout of the fspath->val data had some irregularities
(some unnecessary gaps that stop appearing about halfway),
so I'm not sure there aren't any bugs left in it.

Btrfs: determine level of old roots

2012-10-24T10:36:38+00:00

In btrfs_find_all_roots' termination condition, we compare the level of the
old buffer we got from btrfs_search_old_slot to the level of the current
root node. We'd better compare it to the level of the rewinded root node.

Signed-off-by: Jan Schmidt

btrfs: extended inode ref iteration

2012-10-09T13:15:01+00:00

The iterate_irefs in backref.c is used to build path components from inode
refs. This patch adds code to iterate extended refs as well.

I had modify the callback function signature to abstract out some of the
differences between ref structures. iref_to_path() also needed similar
changes.

Signed-off-by: Mark Fasheh

btrfs: extended inode refs

2012-10-09T13:14:45+00:00

This patch adds basic support for extended inode refs. This includes support
for link and unlink of the refs, which basically gets us support for rename
as well.

Inode creation does not need changing - extended refs are only added after
the ref array is full.

Signed-off-by: Mark Fasheh

Btrfs: use larger limit for translation of logical to inode

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

This is the change of the kernel side.

Translation of logical to inode used to have an upper limit 4k on
inode container's size, but the limit is not large enough for a data
with a great many of refs, so when resolving logical address,
we can end up with
"ioctl ret=0, bytes_left=0, bytes_missing=19944, cnt=510, missed=2493"

This changes to regard 64k as the upper limit and use vmalloc instead of
kmalloc to get memory more easily.

Signed-off-by: Josef Bacik 
Signed-off-by: Liu Bo

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: make aux field of ulist 64 bit

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

Btrfs send/receive uses the aux field to store inode numbers. On
32 bit machines this may become a problem.

Also fix all users of ulist_add and ulist_add_merged.

Reported-by: Arne Jansen 
Signed-off-by: Alexander Block