<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/fs/exportfs, branch v3.2.31</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/fs/exportfs?h=v3.2.31</id>
<link rel='self' href='https://git.amat.us/linux/atom/fs/exportfs?h=v3.2.31'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2011-03-15T06:21:44Z</updated>
<entry>
<title>vfs: Add open by file handle support</title>
<updated>2011-03-15T06:21:44Z</updated>
<author>
<name>Aneesh Kumar K.V</name>
<email>aneesh.kumar@linux.vnet.ibm.com</email>
</author>
<published>2011-01-29T13:13:26Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=becfd1f37544798cbdfd788f32c827160fab98c1'/>
<id>urn:sha1:becfd1f37544798cbdfd788f32c827160fab98c1</id>
<content type='text'>
[AV: duplicate of open() guts removed; file_open_root() used instead]

Signed-off-by: Aneesh Kumar K.V &lt;aneesh.kumar@linux.vnet.ibm.com&gt;
Signed-off-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>exportfs: Return the minimum required handle size</title>
<updated>2011-03-14T13:15:28Z</updated>
<author>
<name>Aneesh Kumar K.V</name>
<email>aneesh.kumar@linux.vnet.ibm.com</email>
</author>
<published>2011-01-29T13:13:25Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=5fe0c2378884e68beb532f5890cc0e3539ac747b'/>
<id>urn:sha1:5fe0c2378884e68beb532f5890cc0e3539ac747b</id>
<content type='text'>
The exportfs encode handle function should return the minimum required
handle size. This helps user to find out the handle size by passing 0
handle size in the first step and then redoing to the call again with
the returned handle size value.

Acked-by: Serge Hallyn &lt;serue@us.ibm.com&gt;
Signed-off-by: Aneesh Kumar K.V &lt;aneesh.kumar@linux.vnet.ibm.com&gt;
Signed-off-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>fs: dcache per-inode inode alias locking</title>
<updated>2011-01-07T06:50:31Z</updated>
<author>
<name>Nick Piggin</name>
<email>npiggin@kernel.dk</email>
</author>
<published>2011-01-07T06:50:06Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=873feea09ebc980cbd3631b767356ce1eee65ec1'/>
<id>urn:sha1:873feea09ebc980cbd3631b767356ce1eee65ec1</id>
<content type='text'>
dcache_inode_lock can be replaced with per-inode locking. Use existing
inode-&gt;i_lock for this. This is slightly non-trivial because we sometimes
need to find the inode from the dentry, which requires d_inode to be
stabilised (either with refcount or d_lock).

Signed-off-by: Nick Piggin &lt;npiggin@kernel.dk&gt;
</content>
</entry>
<entry>
<title>fs: dcache rationalise dget variants</title>
<updated>2011-01-07T06:50:24Z</updated>
<author>
<name>Nick Piggin</name>
<email>npiggin@kernel.dk</email>
</author>
<published>2011-01-07T06:49:43Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=dc0474be3e27463d4d4a2793f82366eed906f223'/>
<id>urn:sha1:dc0474be3e27463d4d4a2793f82366eed906f223</id>
<content type='text'>
dget_locked was a shortcut to avoid the lazy lru manipulation when we already
held dcache_lock (lru manipulation was relatively cheap at that point).
However, how that the lru lock is an innermost one, we never hold it at any
caller, so the lock cost can now be avoided. We already have well working lazy
dcache LRU, so it should be fine to defer LRU manipulations to scan time.

Signed-off-by: Nick Piggin &lt;npiggin@kernel.dk&gt;
</content>
</entry>
<entry>
<title>fs: dcache remove dcache_lock</title>
<updated>2011-01-07T06:50:23Z</updated>
<author>
<name>Nick Piggin</name>
<email>npiggin@kernel.dk</email>
</author>
<published>2011-01-07T06:49:38Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=b5c84bf6f6fa3a7dfdcb556023a62953574b60ee'/>
<id>urn:sha1:b5c84bf6f6fa3a7dfdcb556023a62953574b60ee</id>
<content type='text'>
dcache_lock no longer protects anything. remove it.

Signed-off-by: Nick Piggin &lt;npiggin@kernel.dk&gt;
</content>
</entry>
<entry>
<title>fs: scale inode alias list</title>
<updated>2011-01-07T06:50:22Z</updated>
<author>
<name>Nick Piggin</name>
<email>npiggin@kernel.dk</email>
</author>
<published>2011-01-07T06:49:35Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=b23fb0a60379a95e10c671f646b259ea2558421e'/>
<id>urn:sha1:b23fb0a60379a95e10c671f646b259ea2558421e</id>
<content type='text'>
Add a new lock, dcache_inode_lock, to protect the inode's i_dentry list
from concurrent modification. d_alias is also protected by d_lock.

Signed-off-by: Nick Piggin &lt;npiggin@kernel.dk&gt;
</content>
</entry>
<entry>
<title>exportfs: use dget_parent</title>
<updated>2010-10-26T01:26:13Z</updated>
<author>
<name>Christoph Hellwig</name>
<email>hch@infradead.org</email>
</author>
<published>2010-10-13T15:56:37Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=0461ee2616252f1f6cec628990fa913a4282dcf7'/>
<id>urn:sha1:0461ee2616252f1f6cec628990fa913a4282dcf7</id>
<content type='text'>
Use dget_parent instead of opencoding it.  This simplifies the code, but
more importanly prepares for the more complicated locking for a parent
dget in the dcache scale patch series.

Signed-off-by: Al Viro &lt;viro@zeniv.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>nfs: new subdir Documentation/filesystems/nfs</title>
<updated>2009-10-27T23:34:04Z</updated>
<author>
<name>J. Bruce Fields</name>
<email>bfields@citi.umich.edu</email>
</author>
<published>2009-10-27T18:41:35Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=dc7a08166f3a5f23e79e839a8a88849bd3397c32'/>
<id>urn:sha1:dc7a08166f3a5f23e79e839a8a88849bd3397c32</id>
<content type='text'>
We're adding enough nfs documentation that it may as well have its own
subdirectory.

Acked-by: Randy Dunlap &lt;rdunlap@xenotime.net&gt;
Signed-off-by: J. Bruce Fields &lt;bfields@citi.umich.edu&gt;
</content>
</entry>
<entry>
<title>Merge branch 'next' into for-linus</title>
<updated>2008-12-25T00:40:09Z</updated>
<author>
<name>James Morris</name>
<email>jmorris@namei.org</email>
</author>
<published>2008-12-25T00:40:09Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=cbacc2c7f066a1e01b33b0e27ae5efbf534bc2db'/>
<id>urn:sha1:cbacc2c7f066a1e01b33b0e27ae5efbf534bc2db</id>
<content type='text'>
</content>
</entry>
<entry>
<title>EXPORTFS: handle NULL returns from fh_to_dentry()/fh_to_parent()</title>
<updated>2008-12-09T03:49:32Z</updated>
<author>
<name>J. Bruce Fields</name>
<email>bfields@citi.umich.edu</email>
</author>
<published>2008-12-08T23:24:18Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a4f4d6df537368297a84e6b9444f403f99bf59f6'/>
<id>urn:sha1:a4f4d6df537368297a84e6b9444f403f99bf59f6</id>
<content type='text'>
While 440037287c5 "[PATCH] switch all filesystems over to
d_obtain_alias" removed some cases where fh_to_dentry() and
fh_to_parent() could return NULL, there are still a few NULL returns
left in individual filesystems.  Thus it was a mistake for that commit
to remove the handling of NULL returns in the callers.

Revert those parts of 440037287c5 which removed the NULL handling.

(We could, alternatively, modify all implementations to return -ESTALE
instead of NULL, but that proves to require fixing a number of
filesystems, and in some cases it's arguably more natural to return
NULL.)

Thanks to David for original patch and Linus, Christoph, and Hugh for
review.

Signed-off-by: J. Bruce Fields &lt;bfields@citi.umich.edu&gt;
Cc: David Howells &lt;dhowells@redhat.com&gt;
Cc: Christoph Hellwig &lt;hch@infradead.org&gt;
Cc: Hugh Dickins &lt;hugh@veritas.com&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
</content>
</entry>
</feed>
