<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/fs/xattr.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-05-21T22:31:18Z</updated>
<entry>
<title>fs: xattr_handler table should be const</title>
<updated>2010-05-21T22:31:18Z</updated>
<author>
<name>Stephen Hemminger</name>
</author>
<published>2010-05-14T00:53:14Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=bb4354538eb7b92f32cfedbad68c7be266c0b467'/>
<id>urn:sha1:bb4354538eb7b92f32cfedbad68c7be266c0b467</id>
<content type='text'>
The entries in xattr handler table should be immutable (ie const)
like other operation tables.

Later patches convert common filesystems. Uncoverted filesystems
will still work, but will generate a compiler warning.

Signed-off-by: Stephen Hemminger &lt;shemminger@vyatta.com&gt;
Signed-off-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>sanitize xattr handler prototypes</title>
<updated>2009-12-16T17:16:49Z</updated>
<author>
<name>Christoph Hellwig</name>
</author>
<published>2009-11-13T09:52:56Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=431547b3c4533b8c7fd150ab36980b9a3147797b'/>
<id>urn:sha1:431547b3c4533b8c7fd150ab36980b9a3147797b</id>
<content type='text'>
Add a flags argument to struct xattr_handler and pass it to all xattr
handler methods.  This allows using the same methods for multiple
handlers, e.g. for the ACL methods which perform exactly the same action
for the access and default ACLs, just using a different underlying
attribute.  With a little more groundwork it'll also allow sharing the
methods for the regular user/trusted/secure handlers in extN, ocfs2 and
jffs2 like it's already done for xfs in this patch.

Also change the inode argument to the handlers to a dentry to allow
using the handlers mechnism for filesystems that require it later,
e.g. cifs.

[with GFS2 bits updated by Steven Whitehouse &lt;swhiteho@redhat.com&gt;]

Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
Reviewed-by: James Morris &lt;jmorris@namei.org&gt;
Acked-by: Joel Becker &lt;joel.becker@oracle.com&gt;
Signed-off-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>VFS: Factor out part of vfs_setxattr so it can be called from the SELinux hook for inode_setsecctx.</title>
<updated>2009-09-10T00:11:22Z</updated>
<author>
<name>David P. Quigley</name>
</author>
<published>2009-09-03T18:25:56Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b1ab7e4b2a88d3ac13771463be8f302ce1616cfc'/>
<id>urn:sha1:b1ab7e4b2a88d3ac13771463be8f302ce1616cfc</id>
<content type='text'>
This factors out the part of the vfs_setxattr function that performs the
setting of the xattr and its notification. This is needed so the SELinux
implementation of inode_setsecctx can handle the setting of the xattr while
maintaining the proper separation of layers.

Signed-off-by: David P. Quigley &lt;dpquigl@tycho.nsa.gov&gt;
Acked-by: Serge Hallyn &lt;serue@us.ibm.com&gt;
Signed-off-by: James Morris &lt;jmorris@namei.org&gt;
</content>
</entry>
<entry>
<title>fs: introduce mnt_clone_write</title>
<updated>2009-06-12T01:36:02Z</updated>
<author>
<name>npiggin@suse.de</name>
</author>
<published>2009-04-26T10:25:55Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=96029c4e09ccbd73a6d0ed2b29e80bf2586ad7ef'/>
<id>urn:sha1:96029c4e09ccbd73a6d0ed2b29e80bf2586ad7ef</id>
<content type='text'>
This patch speeds up lmbench lat_mmap test by about another 2% after the
first patch.

Before:
 avg = 462.286
 std = 5.46106

After:
 avg = 453.12
 std = 9.58257

(50 runs of each, stddev gives a reasonable confidence)

It does this by introducing mnt_clone_write, which avoids some heavyweight
operations of mnt_want_write if called on a vfsmount which we know already
has a write count; and mnt_want_write_file, which can call mnt_clone_write
if the file is open for write.

After these two patches, mnt_want_write and mnt_drop_write go from 7% on
the profile down to 1.3% (including mnt_clone_write).

[AV: mnt_want_write_file() should take file alone and derive mnt from it;
not only all callers have that form, but that's the only mnt about which
we know that it's already held for write if file is opened for write]

Cc: Dave Hansen &lt;haveblue@us.ibm.com&gt;
Signed-off-by: Nick Piggin &lt;npiggin@suse.de&gt;
Signed-off-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>xattr: use memdup_user()</title>
<updated>2009-04-21T03:02:50Z</updated>
<author>
<name>Li Zefan</name>
</author>
<published>2009-04-08T07:06:12Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=3939fcde24473dc09ce16e922c88df9b3bee45d9'/>
<id>urn:sha1:3939fcde24473dc09ce16e922c88df9b3bee45d9</id>
<content type='text'>
Remove open-coded memdup_user()

Signed-off-by: Li Zefan &lt;lizf@cn.fujitsu.com&gt;
Signed-off-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>[CVE-2009-0029] System call wrappers part 13</title>
<updated>2009-01-14T13:15:23Z</updated>
<author>
<name>Heiko Carstens</name>
</author>
<published>2009-01-14T13:14:15Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=6a6160a7b5c27b3c38651baef92a14fa7072b3c1'/>
<id>urn:sha1:6a6160a7b5c27b3c38651baef92a14fa7072b3c1</id>
<content type='text'>
Signed-off-by: Heiko Carstens &lt;heiko.carstens@de.ibm.com&gt;
</content>
</entry>
<entry>
<title>[CVE-2009-0029] System call wrappers part 12</title>
<updated>2009-01-14T13:15:23Z</updated>
<author>
<name>Heiko Carstens</name>
</author>
<published>2009-01-14T13:14:14Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=64fd1de3d821659ac0a3004fd5ee1de59e64af30'/>
<id>urn:sha1:64fd1de3d821659ac0a3004fd5ee1de59e64af30</id>
<content type='text'>
Signed-off-by: Heiko Carstens &lt;heiko.carstens@de.ibm.com&gt;
</content>
</entry>
<entry>
<title>[CVE-2009-0029] Convert all system calls to return a long</title>
<updated>2009-01-14T13:15:14Z</updated>
<author>
<name>Heiko Carstens</name>
</author>
<published>2009-01-14T13:13:54Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=2ed7c03ec17779afb4fcfa3b8c61df61bd4879ba'/>
<id>urn:sha1:2ed7c03ec17779afb4fcfa3b8c61df61bd4879ba</id>
<content type='text'>
Convert all system calls to return a long. This should be a NOP since all
converted types should have the same size anyway.
With the exception of sys_exit_group which returned void. But that doesn't
matter since the system call doesn't return.

Signed-off-by: Heiko Carstens &lt;heiko.carstens@de.ibm.com&gt;
</content>
</entry>
<entry>
<title>inode-&gt;i_op is never NULL</title>
<updated>2009-01-05T16:54:28Z</updated>
<author>
<name>Al Viro</name>
</author>
<published>2008-12-04T15:06:33Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=acfa4380efe77e290d3a96b11cd4c9f24f4fbb18'/>
<id>urn:sha1:acfa4380efe77e290d3a96b11cd4c9f24f4fbb18</id>
<content type='text'>
We used to have rather schizophrenic set of checks for NULL -&gt;i_op even
though it had been eliminated years ago.  You'd need to go out of your
way to set it to NULL explicitly _and_ a bunch of code would die on
such inodes anyway.  After killing two remaining places that still
did that bogosity, all that crap can go away.

Signed-off-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>[PATCH] sanitize __user_walk_fd() et.al.</title>
<updated>2008-07-27T00:53:34Z</updated>
<author>
<name>Al Viro</name>
</author>
<published>2008-07-22T13:59:21Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=2d8f30380ab8c706f4e0a8f1aaa22b5886e9ac8a'/>
<id>urn:sha1:2d8f30380ab8c706f4e0a8f1aaa22b5886e9ac8a</id>
<content type='text'>
* do not pass nameidata; struct path is all the callers want.
* switch to new helpers:
	user_path_at(dfd, pathname, flags, &amp;path)
	user_path(pathname, &amp;path)
	user_lpath(pathname, &amp;path)
	user_path_dir(pathname, &amp;path)  (fail if not a directory)
  The last 3 are trivial macro wrappers for the first one.
* remove nameidata in callers.

Signed-off-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;
</content>
</entry>
</feed>
