Comment 21 for bug 769927

I just spotted a truckload of upstream NFS fixes that rolled in with the 2.6.38-10.46 kernel that just hit the repos. Surely ONE of these fixes will resolve this issue.

Here's the NFS changes alone:

  * nfsd4: fix struct file leak on delegation
    - LP: #775809
  * nfsd4: Fix filp leak
    - LP: #775809
  * nfs: don't lose MS_SYNCHRONOUS on remount of noac mount
    - LP: #775809
  * NFSv4.1: Ensure state manager thread dies on last umount
    - LP: #775809
  * nfsd: fix auth_domain reference leak on nlm operations
    - LP: #761134
  * nfsd4: fix oops on lock failure
    - LP: #761134
 * NFS: Fix panic after nfs_umount()
    - LP: #683938
  * NFS: Fix a reference leak in nfs_wb_cancel_page()
  * NFS: Try to commit unstable writes in nfs_release_page()
  * 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: Fix an Oops when truncating a file
  * NFS: Fix a umount race
  * NFS: Fix a bug in nfs_fscache_release_page()
  * NFS: Fix the mapping of the NFSERR_SERVERFAULT error
  * NFS: Too many GETATTR and ACCESS calls after direct I/O
  * nfsd: Fix sort_pacl in fs/nfsd/nf4acl.c to actually sort groups
  * NFS: Revert default r/wsize behavior
  * nfsd: make sure data is on disk before calling ->fsync
  * NFS: Fix nfs_migrate_page()