tree 61a2953e59b5883f376e5b6ba3938fa2721c97be
parent 0a24325e6d8cfb150eba0aa279615ef27b5f6aec
author Josef Bacik <josef@redhat.com> 1252699880 -0400
committer Chris Mason <chris.mason@oracle.com> 1253575429 -0400

Btrfs: fix bitmap size tracking

When we first go to add free space, we allocate a new info and set the offset
and bytes to the space we are adding.  This is fine, except we actually set the
size of a bitmap as we set the bits in it, so if we add space to a bitmap, we'd
end up counting the same space twice.  This isn't a huge deal, it just makes
the allocator behave weirdly since it will think that a bitmap entry has more
space than it ends up actually having.  I used a BUG_ON() to catch when this
problem happened, and with this patch I no longer get the BUG_ON().

Signed-off-by: Josef Bacik <jbacik@redhat.com>
Signed-off-by: Chris Mason <chris.mason@oracle.com>