On Mon, Apr 13, 2015 at 02:39:48PM +0800, Zhao Lei wrote: > > From: Eryu Guan [mailto:eguan@xxxxxxxxxx] > > Sent: Monday, April 13, 2015 1:57 PM > > To: Zhaolei > > Cc: fstests@xxxxxxxxxxxxxxx > > Subject: Re: [PATCH v2] Fix caller's argument for _require_command() > > > > On Mon, Apr 13, 2015 at 12:32:43PM +0800, Zhaolei wrote: > > > From: Zhao Lei <zhaolei@xxxxxxxxxxxxxx> > > > > > > _require_command() only accept 2 arguments, first one is pure command, > > > and second one is name for error message. > > > ..... > > > diff --git a/common/rc b/common/rc > > > index c1a50f2..02ac02a 100644 > > > --- a/common/rc > > > +++ b/common/rc > > > @@ -2923,9 +2923,6 @@ init_rc() > > > $DF_PROG $TEST_DEV > > > exit 1 > > > fi > > > - # Figure out if we need to add -F ("foreign", deprecated) option to xfs_io > > > - xfs_io -c stat $TEST_DIR 2>&1 | grep -q "is not on an XFS filesystem" && \ > > > - export XFS_IO_PROG="$XFS_IO_PROG -F" > > > > I think we should keep the "-F" option, as xfs_io comes with distrobutions like > > RHEL6 still needs "-F" to proceed on non-xfs fs. > > > > [root@dhcp-66-86-3 xfstests]# xfs_io -f -c "pwrite 0 1k" testfile > > xfs_io: specified file ["testfile"] is not on an XFS filesystem > > > I keep -F in v1, and v2 deleted above -F support by suggestion of > Lukáš Czerner <lczerner@xxxxxxxxxx>, who is also author of > these code block. > > CC: Lukáš Czerner <lczerner@xxxxxxxxxx> > > If we suppose xfstests always runs in, and test newest kernel and user tools, > we can remove obsoleted commands. No, absolutely not. xfstests needs to run on all sorts of different kernels and systems, including old vendor kernels. That means dropping compatibility support for them is not an option until their QA departments are no longer testing those distros. IOWs, it's going to be many years before we can drop the "-F" option.... Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx -- 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
