<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/fs/btrfs/inode-map.c, branch linux-2.6.37.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.37.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.37.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2009-09-21T19:56:00Z</updated>
<entry>
<title>Btrfs: do not reuse objectid of deleted snapshot/subvol</title>
<updated>2009-09-21T19:56:00Z</updated>
<author>
<name>Yan, Zheng</name>
</author>
<published>2009-09-21T19:56:00Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=13a8a7c8c47e542b3cdb45bec3f431f96af79361'/>
<id>urn:sha1:13a8a7c8c47e542b3cdb45bec3f431f96af79361</id>
<content type='text'>
The new back reference format does not allow reusing objectid of
deleted snapshot/subvol. So we use ++highest_objectid to allocate
objectid for new snapshot/subvol.

Now we use ++highest_objectid to allocate objectid for both new inode
and new snapshot/subvolume, so this patch removes 'find hole' code in
btrfs_find_free_objectid.

Signed-off-by: Yan Zheng &lt;zheng.yan@oracle.com&gt;
Signed-off-by: Chris Mason &lt;chris.mason@oracle.com&gt;
</content>
</entry>
<entry>
<title>Btrfs: Fix a trivial warning using max() of u64 vs ULL.</title>
<updated>2009-04-27T12:37:49Z</updated>
<author>
<name>Joel Becker</name>
</author>
<published>2009-04-21T19:38:30Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e63b6a6c0ffa2ebd8617cc1a10969000296831aa'/>
<id>urn:sha1:e63b6a6c0ffa2ebd8617cc1a10969000296831aa</id>
<content type='text'>
A small warning popped up on ia64 because inode-map.c was comparing a
u64 object id with the ULL FIRST_FREE_OBJECTID.  My first thought was
that all the OBJECTID constants should contain the u64 cast because
btrfs code deals entirely in u64s.  But then I saw how large that was,
and figured I'd just fix the max() call.

Signed-off-by: Joel Becker &lt;joel.becker@oracle.com&gt;
Signed-off-by: Chris Mason &lt;chris.mason@oracle.com&gt;
</content>
</entry>
<entry>
<title>Btrfs: remove btrfs_init_path</title>
<updated>2009-02-12T19:11:25Z</updated>
<author>
<name>Jeff Mahoney</name>
</author>
<published>2009-02-12T19:11:25Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e00f7308658622fbd483cb0d9fe41165bf9050d0'/>
<id>urn:sha1:e00f7308658622fbd483cb0d9fe41165bf9050d0</id>
<content type='text'>
btrfs_init_path was initially used when the path objects were on the
stack.  Now all the work is done by btrfs_alloc_path and btrfs_init_path
isn't required.

This patch removes it, and just uses kmem_cache_zalloc to zero out the object.

Signed-off-by: Chris Mason &lt;chris.mason@oracle.com&gt;

</content>
</entry>
<entry>
<title>Btrfs: Fix checkpatch.pl warnings</title>
<updated>2009-01-06T02:25:51Z</updated>
<author>
<name>Chris Mason</name>
</author>
<published>2009-01-06T02:25:51Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d397712bcc6a759a560fd247e6053ecae091f958'/>
<id>urn:sha1:d397712bcc6a759a560fd247e6053ecae091f958</id>
<content type='text'>
There were many, most are fixed now.  struct-funcs.c generates some warnings
but these are bogus.

Signed-off-by: Chris Mason &lt;chris.mason@oracle.com&gt;
</content>
</entry>
<entry>
<title>Btrfs: extent_map and data=ordered fixes for space balancing</title>
<updated>2008-09-26T14:05:38Z</updated>
<author>
<name>Zheng Yan</name>
</author>
<published>2008-09-26T14:05:38Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=5b21f2ed3f2947b5195b65c9fdbdd9e52904cc03'/>
<id>urn:sha1:5b21f2ed3f2947b5195b65c9fdbdd9e52904cc03</id>
<content type='text'>
* Add an EXTENT_BOUNDARY state bit to keep the writepage code
from merging data extents that are in the process of being
relocated.  This allows us to do accounting for them properly.

* The balancing code relocates data extents indepdent of the underlying
inode.  The extent_map code was modified to properly account for
things moving around (invalidating extent_map caches in the inode).

* Don't take the drop_mutex in the create_subvol ioctl.  It isn't
required.

* Fix walking of the ordered extent list to avoid races with sys_unlink

* Change the lock ordering rules.  Transaction start goes outside
the drop_mutex.  This allows btrfs_commit_transaction to directly
drop the relocation trees.

Signed-off-by: Chris Mason &lt;chris.mason@oracle.com&gt;
</content>
</entry>
<entry>
<title>Btrfs: Update find free objectid function for orphan cleanup code</title>
<updated>2008-09-25T15:04:07Z</updated>
<author>
<name>Zheng Yan</name>
</author>
<published>2008-09-05T20:43:53Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=6527cdbe68a27a2ee745f36d001aa32d0f46f370'/>
<id>urn:sha1:6527cdbe68a27a2ee745f36d001aa32d0f46f370</id>
<content type='text'>
Orphan items use BTRFS_ORPHAN_OBJECTID (-5UUL) as key objectid. This
affects the find free objectid functions, inode objectid can easily
overflow after orphan file cleanup.

---

Signed-off-by: Chris Mason &lt;chris.mason@oracle.com&gt;
</content>
</entry>
<entry>
<title>Btrfs: Replace the big fs_mutex with a collection of other locks</title>
<updated>2008-09-25T15:04:03Z</updated>
<author>
<name>Chris Mason</name>
</author>
<published>2008-06-25T20:01:30Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=a213501153fd66e2359e091b1612841305ba6551'/>
<id>urn:sha1:a213501153fd66e2359e091b1612841305ba6551</id>
<content type='text'>
Extent alloctions are still protected by a large alloc_mutex.
Objectid allocations are covered by a objectid mutex
Other btree operations are protected by a lock on individual btree nodes

Signed-off-by: Chris Mason &lt;chris.mason@oracle.com&gt;
</content>
</entry>
<entry>
<title>Fix for btrfs_find_free_objectid</title>
<updated>2008-09-25T15:03:59Z</updated>
<author>
<name>Yan</name>
</author>
<published>2008-01-22T17:46:56Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b17854275cd297d40c6c5562fa44a472314c6c7f'/>
<id>urn:sha1:b17854275cd297d40c6c5562fa44a472314c6c7f</id>
<content type='text'>
btrfs_find_free_objectid may return a used objectid due to arithmetic
underflow. This bug may happen when parameter 'root' is tree root,  so
it may cause serious problems when creating snapshot or sub-volume.

Signed-off-by: Chris Mason &lt;chris.mason@oracle.com&gt;
</content>
</entry>
<entry>
<title>Btrfs: Create extent_buffer interface for large blocksizes</title>
<updated>2008-09-25T15:03:56Z</updated>
<author>
<name>Chris Mason</name>
</author>
<published>2007-10-15T20:14:19Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=5f39d397dfbe140a14edecd4e73c34ce23c4f9ee'/>
<id>urn:sha1:5f39d397dfbe140a14edecd4e73c34ce23c4f9ee</id>
<content type='text'>
Signed-off-by: Chris Mason &lt;chris.mason@oracle.com&gt;
</content>
</entry>
<entry>
<title>Btrfs: trivial include fixups</title>
<updated>2007-07-11T14:00:37Z</updated>
<author>
<name>Zach Brown</name>
</author>
<published>2007-07-11T14:00:37Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=ec6b910fb330f29e169c9f502c3ac209515af8d1'/>
<id>urn:sha1:ec6b910fb330f29e169c9f502c3ac209515af8d1</id>
<content type='text'>
Almost none of the files including module.h need to do so,
remove them.

Include sched.h in extent-tree.c to silence a warning about cond_resched()
being undeclared.

Signed-off-by: Zach Brown &lt;zach.brown@oracle.com&gt;
Signed-off-by: Chris Mason &lt;chris.mason@oracle.com&gt;
</content>
</entry>
</feed>
