On Tue, Sep 21, 2010 at 04:46:21PM -0400, Trond Myklebust wrote: > On Tue, 2010-09-21 at 16:24 -0400, J. Bruce Fields wrote: > > On Tue, Sep 21, 2010 at 04:00:32PM -0400, Trond Myklebust wrote: > > > On Tue, 2010-09-21 at 15:36 -0400, Trond Myklebust wrote: > > > > On Tue, 2010-09-21 at 15:20 -0400, J. Bruce Fields wrote: > > > > > All I need to do is mount nfs4.1 and run cthon -s. The last output I > > > > > see from the test is: > > > > > > > > > > check for proper open/unlink operation > > > > > nfsjunk files before unlink: > > > > > > > > > > > > > Oh... I bet I see what it is. > > > > > > > > It's that damned res->sr_slotid = NFS4_MAX_SLOT_TABLE and related > > > > initialisation junk that's biting us in the arse again... > > > > > > > > I'll fix it... > > > > > > Does this work? > > > > Yup. > > It seems to fix things for me too... Once you mentioned NFSv4.1 it was > easy to reproduce the bug. OK, good. I've a slight fear I may have volunteered as Mr. Upstream NFS QA, which I didn't really intend, though of course I want to see stuff caught sooner rather than later.... Anyway, I should have noticed which test it failed on sooner. --b. > > OK. I'll merge these into nfs-for-2.6.37... > > 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
