[Precise][PATCH 0/4] nfs: Kernel Oops on nfs_have_delegation

[Luis Henriques]

BugLink: http://bugs.launchpad.net/bugs/974664

== Precise SRU Justification ==

This bug is preventing users from using NFS clients on Precise.
Several users have reported the issue, which has been already fixed
upstreams but did not made it into stable yet.

== Fix ==

There are four commits that are relevant to fix this issue.  From
mainline kernel:
 - 14977489ffdb80d4caf5a184ba41b23b02fbacd9 (cherry-pick)
 - 96dcadc2fdd111dca90d559f189a30c65394451a (backported)
>From linux-nfs git tree
(git://git.linux-nfs.org/projects/trondmy/linux-nfs.git):
 - 487790f27df9bb27d3400486bd021dd59edc7589 (cherry-pick)
 - 5de4815015e550bdd33f39650554325540356f0c (cherry-pick)

== Impact ==

There are several users reporting the same issue when running NFS
clients on Precise.  Other reports have also been found with the same
issue:

https://bugzilla.redhat.com/show_bug.cgi?id=811138

== Test Case ==

According to one of the bug reporters:

"Logging into a 12.04 client system with autofs5, LDAP, kerberos authenticated
nfs4 mounts. However this is to a server which is running 10.04 (contrary to #4
it seems) In my case the triggering process is gnome-keyring-d."

Trond Myklebust (3):
  NFSv4: Minor cleanups for nfs4_handle_exception and
    nfs4_async_handle_error
  NFSv4: Ensure that the LOCK code sets exception->inode
  NFSv4: Ensure that we check lock exclusive/shared type against open
    modes

William Dauchy (1):
  NFSv4: Rate limit the state manager for lock reclaim warning messages

 fs/nfs/nfs4proc.c  |   33 ++++++++++++++++++++++++++-------
 fs/nfs/nfs4state.c |    5 +++--
 2 files changed, 29 insertions(+), 9 deletions(-)

-- 
1.7.9.5