I'm seeing a problem with the bits in the nfs-for-next branch when I run v4.1. If a bad session is received after a server reboot, the client issues a flood of sequence requests. The sequence RPCs contain the last sequenceID from the previous session with the new sessionID. This is repeated over and over until you ctrl-C the triggering process. The server replies with sequence misordered, but the client issues the exact same RPC over and over. Also to note is that right after the session is destroyed, the client will issue sequence requests with sessionID of 0 right before the create session succeeds. - ricardo > -----Original Message----- > From: Myklebust, Trond > Sent: Friday, December 04, 2009 2:25 PM > To: Adamson, Andy > Cc: linux-nfs@xxxxxxxxxxxxxxx > Subject: Re: [PATCH 0/12] Fix session reset deadlocks Version 4 > > On Fri, 2009-12-04 at 17:01 -0500, Trond Myklebust wrote: > > Those look good to me. I had to fix them up a bit in order to have them > > apply on top of the nfs-for-next branch, but nothing major. > > I figured I might as well push them out immediately. They compile, and > they don't seem to have any adverse effects on the NFSv4 stuff. > > You can find them as the nfs-for-next branch on > git://git.linux-nfs.org/projects/trondmy/nfs-2.6.git > > Cheers > Trond > -- > 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 -- 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
