On Thu, Sep 22, 2016 at 12:20:58PM -0400, Jeff Layton wrote: > I had a go at reproducing this, but no luck. I'm running generic/089 on > a KVM guest client and with the server running on a different KVM > guest. I'm using vhost-scsi to emulate a disk (thanks to Ben Coddington > for the help setting that up, btw...) FYI, I've just used a single guest with both client and server in it to reproduce as well. In that case I'll have to use blocklayout, though as the scsilayout requires separate systems for the reservations. > In any case, I'll poke at it again if I get time. In the meantime, if > you're able to get a vmcore, maybe take a look and see if you can > figure out what's actually bad there? How far does it get in chasing > the pointer to the cl_lock in release_lock_stateid? How do I get a vmcore under kvm? FYI, in the meantime I've also managed to reproduce it without pNFS, althought it seems to take much longer to trigger. One interesting thing is that it seem to only happen when the host system has a heavy CPU load (e.g. building a kernel). Also I think I've always only reproduce it as part of a xfstests ./check -nfs -g auto, never by just running the test standalone. -- 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
