<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/fs/hfsplus/super.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>2010-10-29T08:16:13Z</updated>
<entry>
<title>new helper: mount_bdev()</title>
<updated>2010-10-29T08:16:13Z</updated>
<author>
<name>Al Viro</name>
</author>
<published>2010-07-24T20:46:55Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=152a08366671080f27b32e0c411ad620c5f88b57'/>
<id>urn:sha1:152a08366671080f27b32e0c411ad620c5f88b57</id>
<content type='text'>
... and switch of the obvious get_sb_bdev() users to -&gt;mount()

Signed-off-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>hfsplus: use atomic bitops for the superblock flags</title>
<updated>2010-10-01T03:45:20Z</updated>
<author>
<name>Christoph Hellwig</name>
</author>
<published>2010-10-01T03:45:20Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=84adede31267af37141da2b2b04293c5ea8af7ae'/>
<id>urn:sha1:84adede31267af37141da2b2b04293c5ea8af7ae</id>
<content type='text'>
The flags in the HFS+-specific superlock do get modified during runtime,
use atomic bitops to make the modifications SMP safe.

Signed-off-by: Christoph Hellwig &lt;hch@tuxera.com&gt;
</content>
</entry>
<entry>
<title>hfsplus: add per-superblock lock for volume header updates</title>
<updated>2010-10-01T03:45:08Z</updated>
<author>
<name>Christoph Hellwig</name>
</author>
<published>2010-10-01T03:45:08Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=7ac9fb9c2a50963b699b3548e6f00698c1554dc6'/>
<id>urn:sha1:7ac9fb9c2a50963b699b3548e6f00698c1554dc6</id>
<content type='text'>
Lock updates to the mutal fields in the volume header, and document the
locing in the hfsplus_sb_info structure.

Signed-off-by: Christoph Hellwig &lt;hch@tuxera.com&gt;
</content>
</entry>
<entry>
<title>hfsplus: remove the rsrc_inodes list</title>
<updated>2010-10-01T03:44:02Z</updated>
<author>
<name>Christoph Hellwig</name>
</author>
<published>2010-10-01T03:44:02Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=58a818f532e83f337689358c102ba2048d1b37f5'/>
<id>urn:sha1:58a818f532e83f337689358c102ba2048d1b37f5</id>
<content type='text'>
We never walk the list - the only reason for it is to make the resource fork
inodes appear hashed to the writeback code.  Borrow a trick from JFS to do
that without needing a list head.

Signed-off-by: Christoph Hellwig &lt;hch@tuxera.com&gt;
</content>
</entry>
<entry>
<title>hfsplus: do not cache and write next_alloc</title>
<updated>2010-10-01T03:43:58Z</updated>
<author>
<name>Christoph Hellwig</name>
</author>
<published>2010-10-01T03:43:58Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=66e5db05bb6670f314d90aba5998e6a033e4d563'/>
<id>urn:sha1:66e5db05bb6670f314d90aba5998e6a033e4d563</id>
<content type='text'>
We never look at it, nor change the next_alloc field in the superblock.  So
don't bother caching it or writing it out in hfsplus_sync_fs.

Signed-off-by: Christoph Hellwig &lt;hch@tuxera.com&gt;
</content>
</entry>
<entry>
<title>hfsplus: clean up hfsplus_write_inode</title>
<updated>2010-10-01T03:43:43Z</updated>
<author>
<name>Christoph Hellwig</name>
</author>
<published>2010-10-01T03:43:43Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b5080f77ed2de3c8ac67a63044f8a781c75207d9'/>
<id>urn:sha1:b5080f77ed2de3c8ac67a63044f8a781c75207d9</id>
<content type='text'>
Add a new hfsplus_system_write_inode for writing the special system inodes
and streamline the fastpath write_inode code.

Signed-off-by: Christoph Hellwig &lt;hch@tuxera.com&gt;
</content>
</entry>
<entry>
<title>hfsplus: clean up hfsplus_iget</title>
<updated>2010-10-01T03:43:41Z</updated>
<author>
<name>Christoph Hellwig</name>
</author>
<published>2010-10-01T03:43:41Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=fc4fff82104fa096eada73943fe5249500acd5fa'/>
<id>urn:sha1:fc4fff82104fa096eada73943fe5249500acd5fa</id>
<content type='text'>
Add a new hfsplus_system_read_inode for reading the special system inodes
and streamline the fastpath iget code.

Signed-off-by: Christoph Hellwig &lt;hch@tuxera.com&gt;
</content>
</entry>
<entry>
<title>hfsplus: fix HFSPLUS_I calling convention</title>
<updated>2010-10-01T03:43:31Z</updated>
<author>
<name>Christoph Hellwig</name>
</author>
<published>2010-10-01T03:43:31Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=6af502de224c3742936d54eee7e3690c09822934'/>
<id>urn:sha1:6af502de224c3742936d54eee7e3690c09822934</id>
<content type='text'>
HFSPLUS_I doesn't return a pointer to the hfsplus-specific inode
information like all other FOO_I macros, but dereference the pointer in a way
that made it look like a direct struct derefence.  This only works as long
as the HFSPLUS_I macro is used directly and prevents us from keepig a local
hfsplus_inode_info pointer.  Fix the calling convention and introduce a local
hip variable in all functions that use it constantly.

Signed-off-by: Christoph Hellwig &lt;hch@tuxera.com&gt;
</content>
</entry>
<entry>
<title>hfsplus: fix HFSPLUS_SB calling convention</title>
<updated>2010-10-01T03:42:59Z</updated>
<author>
<name>Christoph Hellwig</name>
</author>
<published>2010-10-01T03:42:59Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=dd73a01a30d729e8fa6f829c4582650e258e36f9'/>
<id>urn:sha1:dd73a01a30d729e8fa6f829c4582650e258e36f9</id>
<content type='text'>
HFSPLUS_SB doesn't return a pointer to the hfsplus-specific superblock
information like all other FOO_SB macros, but dereference the pointer in a way
that made it look like a direct struct derefence.  This only works as long
as the HFSPLUS_SB macro is used directly and prevents us from keepig a local
hfsplus_sb_info pointer.  Fix the calling convention and introduce a local
sbi variable in all functions that use it constantly.

Signed-off-by: Christoph Hellwig &lt;hch@tuxera.com&gt;
</content>
</entry>
<entry>
<title>hfsplus: remove BKL from hfsplus_put_super</title>
<updated>2010-10-01T03:41:53Z</updated>
<author>
<name>Christoph Hellwig</name>
</author>
<published>2010-10-01T03:41:53Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e753a62156e952fd5a3c64f98454d9aeee3a2546'/>
<id>urn:sha1:e753a62156e952fd5a3c64f98454d9aeee3a2546</id>
<content type='text'>
Except for -&gt;put_super the BKL is now gone from HFS, which means it's
superflous there too as -&gt;put_super is serialized by the VFS.

Signed-off-by: Christoph Hellwig &lt;hch@tuxera.com&gt;
</content>
</entry>
</feed>
