On v3.12, running "make -j16 test" on a git.git checkout produces random failures in the test suite, whereas it works fine on v3.11. Git's test suite puts a lot of load on the VFS; re-running failed tests individually when the system is unloaded lets them pass. I haven't been able to get a specific syscall strace of what's going on, but some of the failures I investigated had obvious oddness, like "grep foo bar" returning non-zero, but then looking in "bar" manually shows that it contains the expected content. I bisected this to 232d2d6 (dcache: Translating dentry into pathname without taking rename_lock, 2013-09-09), and can reliably reproduce the problem (and running with the parent ac83871 reliably works). I see the problem on my ext4-over-dmcrypt disk, but also when running the tests on a tmpfs disk. So I don't think it's filesystem-specific. Reading the patch for 232d2d6, it seems plausible that it's a locking problem in the new code, but I don't see anything obviously wrong. I'd expect others can reproduce by running git's test suite, but if not, I'm happy to test patches. -Peff -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
