Luis Henriques <luis.henriques@...> writes: > > On Thu, Apr 19, 2012 at 05:29:09PM +0000, Myklebust, Trond wrote: > > On Thu, 2012-04-19 at 14:48 +0100, Luis Henriques wrote: > > > On Thu, Apr 19, 2012 at 10:30:25AM +0100, Luis Henriques wrote: > > > > On Wed, Apr 18, 2012 at 01:36:52PM -0400, Trond Myklebust wrote: > > > > > The first patch addresses the Oops. > > > > > The second will hopefully address the looping. > > > > > > > > > > Trond Myklebust (2): > > > > > NFSv4: Ensure that the LOCK code sets exception->inode > > > > > NFSv4: Ensure that we check lock exclusive/shared type against open > > > > > modes > > > > > > > > > > fs/nfs/nfs4proc.c | 23 +++++++++++++++++++++-- > > > > > 1 files changed, 21 insertions(+), 2 deletions(-) I use kernel 3.7.1 from kernel.org which has the patches included, which should fix the problems (I checked the source code). But: I get "NFS: nfs4_reclaim_open_state: Lock reclaim failed!" on the client, which mounts home over nfs4. I get senseless network traffic (50MB/s on my gigabit network). Finally I get Kernel Ops on the Server sometimes. -- 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
