On 2016-10-25 14:52:39 [+0800], kernel test robot wrote: > > FYI, we noticed the following commit: > > https://github.com/0day-ci/linux Sebastian-Andrzej-Siewior/NFSv4-replace-seqcount_t-with-a-seqlock_t/20161022-013104 > commit 931437ee2c100a50c36771c947ce3674f8160592 ("NFSv4: replace seqcount_t with a seqlock_t") > > in testcase: ebizzy > with following parameters: > > nr_threads: 200% > iterations: 100x > duration: 10s > > > ebizzy is designed to generate a workload resembling common web application server workloads. > > > on test machine: qemu-system-x86_64 -enable-kvm -cpu kvm64,+ssse3 -m 1G It can't get it triggered. In fact I never get even close to the code path. I tried NFS as rootfs and this test of yours. And I tried "xfstests-dev -nfs" with no luck. So you have NFS as your rootfs. Anything special on the server side? It seems to be a basic NFSv4 export. Sebastian -- 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
