On Jan 25, 2010, at 4:57 PM, Trond Myklebust wrote:
I've committed the following patches to the 'bugfixes' branch for
merging into mainline before the release of 2.6.33. Please review
Reviewed-by: Chuck Lever <chuck.lever@xxxxxxxxxx>
I checked for mechanical problems. The semantics of NFSv4 locking is
beyond me, but fortunately the changes looked mostly obvious.
Cheers
Trond
---
David Howells (1):
NFS: Avoid warnings when CONFIG_NFS_V4=n
H Hartley Sweeten (1):
NFS: Make nfs_commitdata_release static
Trond Myklebust (6):
NFS: Ensure that we handle NFS4ERR_STALE_STATEID correctly
NFSv4.1: Don't call nfs4_schedule_state_recovery() unnecessarily
NFSv4: Don't allow posix locking against servers that don't
support it
NFSv4: Ensure that the NFSv4 locking can recover from stateid
errors
NFS: Try to commit unstable writes in nfs_release_page()
NFS: Fix a reference leak in nfs_wb_cancel_page()
fs/nfs/file.c | 2 +
fs/nfs/nfs4_fs.h | 2 +
fs/nfs/nfs4proc.c | 78 ++++++++++++++++++++++++++++++++++++++
+-------------
fs/nfs/nfs4state.c | 2 +
fs/nfs/sysctl.c | 2 +
fs/nfs/write.c | 3 +-
6 files changed, 67 insertions(+), 22 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs"
in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Chuck Lever
chuck[dot]lever[at]oracle[dot]com
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
