> -----Original Message----- > From: linux-nfs-owner@xxxxxxxxxxxxxxx [mailto:linux-nfs- > owner@xxxxxxxxxxxxxxx] On Behalf Of Dick Streefland > Sent: Friday, September 07, 2012 9:57 AM > To: linux-nfs@xxxxxxxxxxxxxxx > Subject: Re: [3.2.5] NFSv3 CLOSE_WAIT hang > > "Myklebust, Trond" <Trond.Myklebust@xxxxxxxxxx> wrote: > | Clearly the comment is misleading and should be removed. That write > | lock > | > | _is_ needed in order to throttle slots on TCP. > | > | As far as I know, kernel 3.3 is not in stable support any more, so I > | can't help that. Can you reproduce the problem on a 3.5 kernel or > | higher? > > I can easily reproduce the hang on the latest kernel (eeea3ac912) with my > script (http://permalink.gmane.org/gmane.linux.nfs/51833). On TCP? > With this change, it doesn't hang: It doesn't matter as long as that change is wrong. That code _is_ needed for TCP. Now if UDP is broken, then we can talk about a fix for that issue, but that's not going to be the one you propose. 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
