PATCH info

The following set of patches fix known issues with the 2.6.27 NFS client code, and significantly enhance the support for NFSv4.

linux-2.6.27-000-nlinks_must_set_invalidate_flag.dif:

From: Trond Myklebust <Trond.Myklebust@netapp.com>

Date: Tue, 14 Oct 2008 19:23:07 -0400

NFS: Changes to inode->i_nlinks must set the NFS_INO_INVALID_ATTR flag

Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>

linux-2.6.27-001-simplify_last_updated.dif:

From: Trond Myklebust <Trond.Myklebust@netapp.com>

Date: Tue, 14 Oct 2008 19:16:07 -0400

NFS: Fix the resolution problem with nfs_inode_attrs_need_update()

It appears that 'jiffies' timestamps do not have high enough resolution for nfs_inode_attrs_need_update(). One problem is that a GETATTR can be launched within < 1 jiffy of the last operation that updated the attribute. Another problem is that RPC calls can take < 1 jiffy to execute.

We can fix this by switching the variables to use a simple global counter that gets incremented every time we start another GETATTR call.

Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>

linux-2.6.27-002-fix_cache_change_attribute.dif:

From: Trond Myklebust <Trond.Myklebust@netapp.com>

Date: Tue, 14 Oct 2008 19:24:50 -0400

NFS: Fix a resolution problem with nfs_inode->cache_change_attribute

The cache_change_attribute is used to decide whether or not a directory has changed, in which case we may need to look it up again. Again, the use of 'jiffies' leads to an issue of resolution.

Once again, the fix is to change nfs_inode->cache_change_attribute, and just make it a simple counter.

Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>

Name	Last modified	Size

Parent Directory		-
linux-2.6.27-000-nli..>	2008-10-14 23:29	801
linux-2.6.27-001-sim..>	2008-10-14 23:29	8.4K
linux-2.6.27-002-fix..>	2008-10-14 23:29	1.4K
series	2008-10-14 23:29	221

NFS client patches for Linux 2.6.27