<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/fs/jfs/file.c, branch linux-2.6.34.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.34.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.34.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2010-03-04T23:20:30Z</updated>
<entry>
<title>dquot: cleanup dquot initialize routine</title>
<updated>2010-03-04T23:20:30Z</updated>
<author>
<name>Christoph Hellwig</name>
</author>
<published>2010-03-03T14:05:07Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=871a293155a24554e153538d36e3a80fa169aefb'/>
<id>urn:sha1:871a293155a24554e153538d36e3a80fa169aefb</id>
<content type='text'>
Get rid of the initialize dquot operation - it is now always called from
the filesystem and if a filesystem really needs it's own (which none
currently does) it can just call into it's own routine directly.

Rename the now static low-level dquot_initialize helper to __dquot_initialize
and vfs_dq_init to dquot_initialize to have a consistent namespace.

Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
Signed-off-by: Jan Kara &lt;jack@suse.cz&gt;
</content>
</entry>
<entry>
<title>dquot: move dquot initialization responsibility into the filesystem</title>
<updated>2010-03-04T23:20:30Z</updated>
<author>
<name>Christoph Hellwig</name>
</author>
<published>2010-03-03T14:05:06Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=907f4554e2521cb28b0009d17167760650a9561c'/>
<id>urn:sha1:907f4554e2521cb28b0009d17167760650a9561c</id>
<content type='text'>
Currently various places in the VFS call vfs_dq_init directly.  This means
we tie the quota code into the VFS.  Get rid of that and make the
filesystem responsible for the initialization.   For most metadata operations
this is a straight forward move into the methods, but for truncate and
open it's a bit more complicated.

For truncate we currently only call vfs_dq_init for the sys_truncate case
because open already takes care of it for ftruncate and open(O_TRUNC) - the
new code causes an additional vfs_dq_init for those which is harmless.

For open the initialization is moved from do_filp_open into the open method,
which means it happens slightly earlier now, and only for regular files.
The latter is fine because we don't need to initialize it for operations
on special files, and we already do it as part of the namespace operations
for directories.

Add a dquot_file_open helper that filesystems that support generic quotas
can use to fill in -&gt;open.

Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
Signed-off-by: Jan Kara &lt;jack@suse.cz&gt;
</content>
</entry>
<entry>
<title>dquot: cleanup dquot transfer routine</title>
<updated>2010-03-04T23:20:29Z</updated>
<author>
<name>Christoph Hellwig</name>
</author>
<published>2010-03-03T14:05:03Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b43fa8284d7790d9cca32c9c55e24f29be2fa33b'/>
<id>urn:sha1:b43fa8284d7790d9cca32c9c55e24f29be2fa33b</id>
<content type='text'>
Get rid of the transfer dquot operation - it is now always called from
the filesystem and if a filesystem really needs it's own (which none
currently does) it can just call into it's own routine directly.

Rename the now static low-level dquot_transfer helper to __dquot_transfer
and vfs_dq_transfer to dquot_transfer to have a consistent namespace,
and make the new dquot_transfer return a normal negative errno value
which all callers expect.

Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
Signed-off-by: Jan Kara &lt;jack@suse.cz&gt;
</content>
</entry>
<entry>
<title>dquot: move dquot transfer responsibility into the filesystem</title>
<updated>2010-03-04T23:20:28Z</updated>
<author>
<name>Christoph Hellwig</name>
</author>
<published>2010-03-03T14:05:02Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=759bfee658beab14af7b357156461d0eb852be2c'/>
<id>urn:sha1:759bfee658beab14af7b357156461d0eb852be2c</id>
<content type='text'>
Currently notify_change calls vfs_dq_transfer directly.  This means
we tie the quota code into the VFS.  Get rid of that and make the
filesystem responsible for the transfer.  Most filesystems already
do this, only ufs and udf need the code added, and for jfs it needs to
be enabled unconditionally instead of only when ACLs are enabled.

Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
Signed-off-by: Jan Kara &lt;jack@suse.cz&gt;
</content>
</entry>
<entry>
<title>jffs2/jfs/xfs: switch over to 'check_acl' rather than 'permission()'</title>
<updated>2009-09-08T18:09:04Z</updated>
<author>
<name>Linus Torvalds</name>
</author>
<published>2009-08-28T19:29:03Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=18f4c644773bc8de1fd9c5182b30c231aafb94ef'/>
<id>urn:sha1:18f4c644773bc8de1fd9c5182b30c231aafb94ef</id>
<content type='text'>
This avoids an indirect call in the VFS for each path component lookup.

Well, at least as long as you own the directory in question, and the ACL
check is unnecessary.

Reviewed-by: James Morris &lt;jmorris@namei.org&gt;
Acked-by: Serge Hallyn &lt;serue@us.ibm.com&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>BKL-removal: Implement a compat_ioctl handler for JFS</title>
<updated>2008-02-07T19:45:29Z</updated>
<author>
<name>Andi Kleen</name>
</author>
<published>2008-01-27T23:02:02Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=ef1fc2f01e02951a0d8520ec3aa0b38606d74b55'/>
<id>urn:sha1:ef1fc2f01e02951a0d8520ec3aa0b38606d74b55</id>
<content type='text'>
The ioctls were already compatible except for the actual values so this
was fairly easy to do.

Signed-off-by: Andi Kleen &lt;ak@suse.de&gt;
Signed-off-by: Dave Kleikamp &lt;shaggy@linux.vnet.ibm.com&gt;
</content>
</entry>
<entry>
<title>BKL-removal: Use unlocked_ioctl for jfs</title>
<updated>2008-02-07T19:33:58Z</updated>
<author>
<name>Andi Kleen</name>
</author>
<published>2008-01-27T22:58:51Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=baab81fa518ecfac597402b462631f5593926623'/>
<id>urn:sha1:baab81fa518ecfac597402b462631f5593926623</id>
<content type='text'>
Convert jfs_ioctl over to not use the BKL. The only potential race
I could see was with two ioctls in parallel changing the flags
and losing the updates. Use the i_mutex to protect against this.

Signed-off-by: Andi Kleen &lt;ak@suse.de&gt;
Signed-off-by: Dave Kleikamp &lt;shaggy@linux.vnet.ibm.com&gt;
</content>
</entry>
<entry>
<title>sendfile: remove .sendfile from filesystems that use generic_file_sendfile()</title>
<updated>2007-07-10T06:04:13Z</updated>
<author>
<name>Jens Axboe</name>
</author>
<published>2007-06-01T09:49:19Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=5ffc4ef45b3b0a57872f631b4e4ceb8ace0d7496'/>
<id>urn:sha1:5ffc4ef45b3b0a57872f631b4e4ceb8ace0d7496</id>
<content type='text'>
They can use generic_file_splice_read() instead. Since sys_sendfile() now
prefers that, there should be no change in behaviour.

Signed-off-by: Jens Axboe &lt;jens.axboe@oracle.com&gt;
</content>
</entry>
<entry>
<title>[PATCH] mark struct inode_operations const 2</title>
<updated>2007-02-12T17:48:46Z</updated>
<author>
<name>Arjan van de Ven</name>
</author>
<published>2007-02-12T08:55:39Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=92e1d5be91a0e3ffa5c4697eeb09b2aa22792122'/>
<id>urn:sha1:92e1d5be91a0e3ffa5c4697eeb09b2aa22792122</id>
<content type='text'>
Many struct inode_operations in the kernel can be "const".  Marking them const
moves these to the .rodata section, which avoids false sharing with potential
dirty data.  In addition it'll catch accidental writes at compile time to
these shared resources.

Signed-off-by: Arjan van de Ven &lt;arjan@linux.intel.com&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
<entry>
<title>jfs: Add splice support</title>
<updated>2006-10-30T17:47:02Z</updated>
<author>
<name>Daniel Drake</name>
</author>
<published>2006-10-30T17:47:02Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=89f68225876db7df638de2884b561facb1870239'/>
<id>urn:sha1:89f68225876db7df638de2884b561facb1870239</id>
<content type='text'>
This allows the splice() and tee() syscalls to be used with JFS.

Signed-off-by: Daniel Drake &lt;ddrake@brontes3d.com&gt;
Signed-off-by: Dave Kleikamp &lt;shaggy@austin.ibm.com&gt;
</content>
</entry>
</feed>
