<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.kerneltrap.org"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>KernelTrap - Trond Myklebust</title>
 <link>http://www.kerneltrap.org/taxonomy/term/901/0</link>
 <description></description>
 <language>en-local</language>
<item>
 <title>NFS Client Updates for 2.6.24</title>
 <link>http://www.kerneltrap.org/Linux/NFS_Client_Updates_for_2.6.24</link>
 <description>&lt;div class=&quot;taxonomy-images&quot;&gt;&lt;a href=&quot;/news/linux&quot; class=&quot;taxonomy-image-links&quot;&gt;&lt;img src=&quot;http://kerneltrap.org/files/category_pictures/K-Linux.gif&quot; alt=&quot;Linux news&quot; title=&quot;Linux news&quot;  width=&quot;75&quot; height=&quot;75&quot; /&gt;&lt;/a&gt;&lt;/div&gt;&lt;!-- google_ad_section_start --&gt;&lt;p&gt;Trond Myklebust noted the &lt;a href=&quot;http://kerneltrap.org/mailarchive/linux-kernel/2007/10/3/328870&quot;&gt;NFS client updates&lt;/a&gt; for the upcoming 2.6.24 kernel:&lt;/p&gt;
&lt;blockquote&gt;&lt;p&gt;&quot;Aside from the usual updates from Chuck for NFS-over-IPv6 (still incomplete) and a number of bugfixes for the text-based mount code, the main news in the NFS tree is the merging of support for the NFS/RDMA client code from Tom Talpey and the NetApp New England (NANE) team.&quot;&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;He continued, &quot;&lt;i&gt;we also have the 64-bit inode support from RedHat/Peter Staubach.  There is also the addition of a nfs_vm_page_mkwrite() method in order to clean up the mmap() write code.  Finally, I&#039;ve been working on a number of updates for the attribute revalidation, having pulled apart most of the dentry and attribute revalidation into separate variables. A number of fixes that address existing bugs fell out of that review, which should hopefully result in more efficient dcache behaviour...&lt;/i&gt;&quot;  Actual source changes can be browsed in the &lt;a href=&quot;http://linux-nfs.org/cgi-bin/gitweb.cgi?p=nfs-2.6.git;a=summary&quot;&gt;NFS client git repository&lt;/a&gt;.&lt;/p&gt;
&lt;!-- google_ad_section_end --&gt;&lt;p&gt;&lt;a href=&quot;http://www.kerneltrap.org/Linux/NFS_Client_Updates_for_2.6.24&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.kerneltrap.org/Linux/NFS_Client_Updates_for_2.6.24#comments</comments>
 <category domain="http://www.kerneltrap.org/2.6.24">2.6.24</category>
 <category domain="http://www.kerneltrap.org/filesystem">filesystem</category>
 <category domain="http://www.kerneltrap.org/taxonomy/term/470">IPv6</category>
 <category domain="http://www.kerneltrap.org/Linux">Linux</category>
 <category domain="http://www.kerneltrap.org/merge_plans">merge plans</category>
 <category domain="http://www.kerneltrap.org/NFS">NFS</category>
 <category domain="http://www.kerneltrap.org/taxonomy/term/901">Trond Myklebust</category>
 <category domain="http://www.kerneltrap.org/news/linux">Linux news</category>
 <pubDate>Thu, 04 Oct 2007 12:31:08 +0000</pubDate>
 <dc:creator>Jeremy</dc:creator>
 <guid isPermaLink="false">14513 at http://www.kerneltrap.org</guid>
</item>
<item>
 <title>Copy on Write Credentials</title>
 <link>http://www.kerneltrap.org/Linux/Copy_on_Write_Credentials</link>
 <description>&lt;div class=&quot;taxonomy-images&quot;&gt;&lt;a href=&quot;/news/linux&quot; class=&quot;taxonomy-image-links&quot;&gt;&lt;img src=&quot;http://kerneltrap.org/files/category_pictures/K-Linux.gif&quot; alt=&quot;Linux news&quot; title=&quot;Linux news&quot;  width=&quot;75&quot; height=&quot;75&quot; /&gt;&lt;/a&gt;&lt;/div&gt;&lt;!-- google_ad_section_start --&gt;&lt;p&gt;&quot;&lt;i&gt;Here&#039;s a new version of my credentials patch.  It&#039;s still very basic, with only Ext3, (V)FAT, NFS, AFS, SELinux and keyrings compiled in on an x86_64 arch kernel,&lt;/i&gt;&quot; &lt;a href=&quot;http://kerneltrap.org/mailarchive/linux-kernel/2007/9/18/262791&quot;&gt;stated David Howells&lt;/a&gt;.  He described the patch as, &quot;&lt;i&gt;introduce a copy on write credentials record (struct cred).  The fsuid, fsgid, supplementary groups list move into it (DAC security).  The session, process and thread keyrings are reflected in it, but don&#039;t primarily reside there as they aren&#039;t per-thread and occasionally need to be instantiated or replaced by other threads or processes.&lt;/i&gt;&quot;&lt;/p&gt;
&lt;p&gt;Casey Schaufler asked, &quot;&lt;i&gt;what I don&#039;t really understand is what value is gained by this exercise.  Are the savings sufficiently significant to justify the effort?&lt;/i&gt;&quot;  Trond Myklebust explained, &quot;&lt;i&gt;it is not about savings, but about new functionality. Basically, the existence of reference-counted credentials will allow AFS and NFS to cache that information and use it for deferred writes etc.&lt;/i&gt;&quot;  David added, &quot;&lt;i&gt;and also make it easier for cachefiles and hopefully NFSd to override the active security.  There&#039;s a comment somewhere in, I think, the SunRPC code in the Linux kernel bemoaning the lack of this very feature:-)&lt;/i&gt;&quot;&lt;/p&gt;
&lt;!-- google_ad_section_end --&gt;&lt;p&gt;&lt;a href=&quot;http://www.kerneltrap.org/Linux/Copy_on_Write_Credentials&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://www.kerneltrap.org/Linux/Copy_on_Write_Credentials#comments</comments>
 <category domain="http://www.kerneltrap.org/taxonomy/term/950">COW</category>
 <category domain="http://www.kerneltrap.org/taxonomy/term/951">David Howells</category>
 <category domain="http://www.kerneltrap.org/Linux">Linux</category>
 <category domain="http://www.kerneltrap.org/NFS">NFS</category>
 <category domain="http://www.kerneltrap.org/taxonomy/term/583">patch</category>
 <category domain="http://www.kerneltrap.org/taxonomy/term/901">Trond Myklebust</category>
 <category domain="http://www.kerneltrap.org/news/linux">Linux news</category>
 <pubDate>Tue, 18 Sep 2007 19:16:19 +0000</pubDate>
 <dc:creator>Jeremy</dc:creator>
 <guid isPermaLink="false">14398 at http://www.kerneltrap.org</guid>
</item>
<item>
 <title>NFS Regression</title>
 <link>http://www.kerneltrap.org/Linux/NFS_Regression</link>
 <description>&lt;div class=&quot;taxonomy-images&quot;&gt;&lt;a href=&quot;/news/linux&quot; class=&quot;taxonomy-image-links&quot;&gt;&lt;img src=&quot;http://kerneltrap.org/files/category_pictures/K-Linux.gif&quot; alt=&quot;Linux news&quot; title=&quot;Linux news&quot;  width=&quot;75&quot; height=&quot;75&quot; /&gt;&lt;/a&gt;&lt;/div&gt;&lt;!-- google_ad_section_start --&gt;&lt;p&gt;Hua Zhong &lt;a href=&quot;http://kerneltrap.org/mailarchive/linux-kernel/2007/8/30/166372&quot;&gt;reported an NFS regression&lt;/a&gt; in 2.6.23-rc4 as compared to 2.6.22, &quot;&lt;i&gt;[upgrading] causes several autofs mounts to fail silently - they just [do] not appear when they should.&lt;/i&gt;&quot;  Trond Myklebust explained that the change to default behavior was intentional to prevent an NFS mount from being mounted with the wrong options.  The patch also introduced a new mount option, &quot;&lt;i&gt;the new option is there in order to make it damned clear to sysadmins that this is a dangerous thing to do: mounts which don&#039;t share the same superblock also don&#039;t share the same data and attribute caches. Any file or directory which appears in both mounts had better only be used by one application at a time or be using an appropriate locking scheme.&lt;/i&gt;&quot;  Jakob Oestergaard defended the change asserting, &quot;&lt;i&gt;what he &#039;broke&#039; is, for example, a ro mount being mounted as rw.  That *could* be a very serious security (etc.etc.) problem which he just fixed. Anything depending on read-only not being enforced will cease to work, of course, and that is what a few people complain about(!).&lt;/i&gt;&quot;&lt;/p&gt;
&lt;p&gt;Linus Torvalds disagreed strongly with the change, &quot;&lt;i&gt;that commit gets reverted or fixed. It&#039;s a regression, and your theories that it&#039;s &#039;better&#039; that way are obviously broken.&lt;/i&gt;&quot;  He added:&lt;/p&gt;
&lt;blockquot