On Fri, Dec 12, 2014 at 12:43:21PM +0800, Eryu Guan wrote: > @@ -136,7 +138,7 @@ _workout() > done > # Following like will check that pid is still run. > # Once fio exit we can stop fallocate/truncate loop > - kill -0 $pid > /dev/null 2>&1 || break > + pgrep fio > /dev/null 2>&1 || break > done > wait $pid This patch is causing generic/299 to loop forever for me. The problem is that "fio" is too easy to match: root@kvm-xfstests:~# pgrep fio 1407 root@kvm-xfstests:~# ps augxww | grep 1407 root 1407 0.0 0.0 0 0 ? S< 16:52 0:00 [dm_bufio_cache] root 8386 0.0 0.0 2704 492 ttyS1 S+ 17:06 0:00 grep 1407 I'm currently a testing a patch which uses "pgrep -f $XFS_IO_PROG" instead, but I'm a bit surprised no once else noticed this, I guess people aren't building their xfstests test kernels with DM_SNAPSHOP or DM_VERITY configured (either of which will seleect DM_BUFIO)? - Ted -- To unsubscribe from this list: send the line "unsubscribe fstests" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
