<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/fs/xfs/xfs_itable.c, branch linux-3.2.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.2.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.2.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2011-04-08T13:09:12Z</updated>
<entry>
<title>xfs: fix variable set but not used warnings</title>
<updated>2011-04-08T13:09:12Z</updated>
<author>
<name>Christoph Hellwig</name>
</author>
<published>2011-04-04T12:55:44Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=ecb697c16c1718ae97bb73ce41a5d5ac2aed29ec'/>
<id>urn:sha1:ecb697c16c1718ae97bb73ce41a5d5ac2aed29ec</id>
<content type='text'>
GCC 4.6 now warnings about variables set but not used.  Fix the trivially
fixable warnings of this sort.

Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
Signed-off-by: Alex Elder &lt;aelder@sgi.com&gt;
</content>
</entry>
<entry>
<title>xfs: Extend project quotas to support 32bit project ids</title>
<updated>2010-10-18T20:08:08Z</updated>
<author>
<name>Arkadiusz Mi?kiewicz</name>
</author>
<published>2010-09-26T06:10:18Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=6743099ce57a40509a86849a22317ed4b7516911'/>
<id>urn:sha1:6743099ce57a40509a86849a22317ed4b7516911</id>
<content type='text'>
This patch adds support for 32bit project quota identifiers.

On disk format is backward compatible with 16bit projid numbers. projid
on disk is now kept in two 16bit values - di_projid_lo (which holds the
same position as old 16bit projid value) and new di_projid_hi (takes
existing padding) and converts from/to 32bit value on the fly.

xfs_admin (for existing fs), mkfs.xfs (for new fs) needs to be used
to enable PROJID32BIT support.

Signed-off-by: Arkadiusz Miśkiewicz &lt;arekm@maven.pl&gt;
Reviewed-by: Christoph Hellwig &lt;hch@lst.de&gt;
Signed-off-by: Alex Elder &lt;aelder@sgi.com&gt;
</content>
</entry>
<entry>
<title>xfs: remove xfs_iput</title>
<updated>2010-07-26T18:16:44Z</updated>
<author>
<name>Christoph Hellwig</name>
</author>
<published>2010-06-24T01:52:50Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f2d6761433d69d94e0b39ac44ef0f0f0b0508065'/>
<id>urn:sha1:f2d6761433d69d94e0b39ac44ef0f0f0b0508065</id>
<content type='text'>
xfs_iput is just a small wrapper for xfs_iunlock + IRELE.  Having this
out of line wrapper means the trace events in those two can't track
their caller properly.  So just remove the wrapper and opencode the
unlock + rele in the few callers.

Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
Reviewed-by: Dave Chinner &lt;dchinner@redhat.com&gt;

</content>
</entry>
<entry>
<title>xfs: remove unneeded #include statements</title>
<updated>2010-07-26T18:16:33Z</updated>
<author>
<name>Christoph Hellwig</name>
</author>
<published>2010-06-23T08:11:15Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=3400777ff03a3cd4fdbc6cb15676fc7e7ceefc00'/>
<id>urn:sha1:3400777ff03a3cd4fdbc6cb15676fc7e7ceefc00</id>
<content type='text'>
Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
Reviewed-by: Dave Chinner &lt;david@fromorbit.com&gt;

</content>
</entry>
<entry>
<title>xfs: drop dmapi hooks</title>
<updated>2010-07-26T18:16:33Z</updated>
<author>
<name>Christoph Hellwig</name>
</author>
<published>2010-06-23T08:11:15Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=288699fecaffa1ef8f75f92020cbb593a772e487'/>
<id>urn:sha1:288699fecaffa1ef8f75f92020cbb593a772e487</id>
<content type='text'>
Dmapi support was never merged upstream, but we still have a lot of hooks
bloating XFS for it, all over the fast pathes of the filesystem.

This patch drops over 700 lines of dmapi overhead.  If we'll ever get HSM
support in mainline at least the namespace events can be done much saner
in the VFS instead of the individual filesystem, so it's not like this
is much help for future work.

Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
Reviewed-by: Dave Chinner &lt;dchinner@redhat.com&gt;

</content>
</entry>
<entry>
<title>xfs: remove block number from inode lookup code</title>
<updated>2010-06-24T01:35:17Z</updated>
<author>
<name>Dave Chinner</name>
</author>
<published>2010-06-24T01:35:17Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=7b6259e7a83647948fa33a736cc832310c8d85aa'/>
<id>urn:sha1:7b6259e7a83647948fa33a736cc832310c8d85aa</id>
<content type='text'>
The block number comes from bulkstat based inode lookups to shortcut
the mapping calculations. We ar enot able to trust anything from
bulkstat, so drop the block number as well so that the correct
lookups and mappings are always done.

Signed-off-by: Dave Chinner &lt;dchinner@redhat.com&gt;
Reviewed-by: Christoph Hellwig &lt;hch@lst.de&gt;
</content>
</entry>
<entry>
<title>xfs: rename XFS_IGET_BULKSTAT to XFS_IGET_UNTRUSTED</title>
<updated>2010-06-24T01:15:47Z</updated>
<author>
<name>Dave Chinner</name>
</author>
<published>2010-06-24T01:15:47Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1920779e67cbf5ea8afef317777c5bf2b8096188'/>
<id>urn:sha1:1920779e67cbf5ea8afef317777c5bf2b8096188</id>
<content type='text'>
Inode numbers may come from somewhere external to the filesystem
(e.g. file handles, bulkstat information) and so are inherently
untrusted. Rename the flag we use for these lookups to make it
obvious we are doing a lookup of an untrusted inode number and need
to verify it completely before trying to read it from disk.

Signed-off-by: Dave Chinner &lt;dchinner@redhat.com&gt;
Reviewed-by: Christoph Hellwig &lt;hch@lst.de&gt;
</content>
</entry>
<entry>
<title>xfs: always use iget in bulkstat</title>
<updated>2010-06-23T08:11:11Z</updated>
<author>
<name>Christoph Hellwig</name>
</author>
<published>2010-06-23T08:11:11Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=7dce11dbac54fce777eea0f5fb25b2694ccd7900'/>
<id>urn:sha1:7dce11dbac54fce777eea0f5fb25b2694ccd7900</id>
<content type='text'>
The non-coherent bulkstat versionsthat look directly at the inode
buffers causes various problems with performance optimizations that
make increased use of just logging inodes.  This patch makes bulkstat
always use iget, which should be fast enough for normal use with the
radix-tree based inode cache introduced a while ago.

Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
Reviewed-by: Dave Chinner &lt;dchinner@redhat.com&gt;
</content>
</entry>
<entry>
<title>xfs: return inode fork offset in bulkstat for fsr</title>
<updated>2010-03-05T17:02:07Z</updated>
<author>
<name>Dave Chinner</name>
</author>
<published>2010-03-05T04:41:14Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=07000ee686cf19e853fa06f7904eff2cfe230ea3'/>
<id>urn:sha1:07000ee686cf19e853fa06f7904eff2cfe230ea3</id>
<content type='text'>
So that fsr can attempt to get the fork offset of the temporary
inode it uses the same as the inode it is defragmenting, pass the
fork offset out in the bulkstat information.

The bulkstat structure has padding that has always been zeroed, so
userspace can tell if this field is set or not by use of the xattr
present flag and a non-zero value for the fork offset.

Signed-off-by: Dave Chinner &lt;dchinner@redhat.com&gt;
Reviewed-by: Christoph Hellwig &lt;hch@lst.de&gt;
Signed-off-by: Alex Elder &lt;aelder@sgi.com&gt;
</content>
</entry>
<entry>
<title>xfs: replace KM_LARGE with explicit vmalloc use</title>
<updated>2010-01-21T19:44:56Z</updated>
<author>
<name>Christoph Hellwig</name>
</author>
<published>2010-01-20T21:55:30Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=bdfb04301fa5fdd95f219539a9a5b9663b1e5fc2'/>
<id>urn:sha1:bdfb04301fa5fdd95f219539a9a5b9663b1e5fc2</id>
<content type='text'>
We use the KM_LARGE flag to make kmem_alloc and friends use vmalloc
if necessary.  As we only need this for a few boot/mount time
allocations just switch to explicit vmalloc calls there.

Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
Signed-off-by: Alex Elder &lt;aelder@sgi.com&gt;
</content>
</entry>
</feed>
