On Mon, Jun 23, 2014 at 04:09:18PM +0200, Lukáš Czerner wrote: > On Mon, 23 Jun 2014, Lukáš Czerner wrote: > > > Date: Mon, 23 Jun 2014 14:35:50 +0200 (CEST) > > From: Lukáš Czerner <lczerner@xxxxxxxxxx> > > To: Filipe David Borba Manana <fdmanana@xxxxxxxxx> > > Cc: fstests@xxxxxxxxxxxxxxx, linux-btrfs@xxxxxxxxxxxxxxx > > Subject: Re: [PATCH] generic/017: skip invalid block sizes for btrfs > > > > On Mon, 23 Jun 2014, Filipe David Borba Manana wrote: > > > > > Date: Mon, 23 Jun 2014 11:28:00 +0100 > > > From: Filipe David Borba Manana <fdmanana@xxxxxxxxx> > > > To: fstests@xxxxxxxxxxxxxxx > > > Cc: linux-btrfs@xxxxxxxxxxxxxxx, > > > Filipe David Borba Manana <fdmanana@xxxxxxxxx> > > > Subject: [PATCH] generic/017: skip invalid block sizes for btrfs > > > > > > In btrfs the block size (called sector size in btrfs) can not be > > > smaller then the page size. Therefore skip block sizes smaller > > > then page size if the fs is btrfs, so that the test can succeed > > > on btrfs (testing only with block sizes of 4kb on systems with a > > > page size of 4Kb). > > > > The test itself is wrong, it's trying to do _scratch_mkfs with > > different block size, but the block size might already be specified > > by the user (in fact it should be user responsibility to test > > different block sizes). In the case that mkfs can not handle > > multiple of the same option like mkfs.xfs for example it will fail, > > but the test will go on with the original file system. > > > > The test needs to be fixed to just test the file system with options > > specified by the user. Also we should change _scratch_mkfs() to fail > > the test if the mkfs failed (no one is actually testing mkfs_status > > variable anyway. > > Correction, _scratch_mkfs_xfs() is actually testing mkfs_status and > will attempt to re-run mkfs only with provided options if it failed > before. But my point remains the same, block size to test should be > in users hands and we should run all tests with different block > sizes, if supported. Follow that line of reasoning to other options. If we take that argument to it's logical conclusion, no test should be able to set any mount or mkfs option because that's for the user to control. This implies we can't even have quota specific tests because they need to override the mount options (and perhaps mkfs options) the user has specified to be properly tested. Some tests only work on specific configurations and therefore they need to be able to control the execution environment directly. Hence the behaviour of _scratch_mkfs_xfs(), where it will *attempt* to use the user provided options. However, if they conflict with what the test requires it will drop the user options and use what the test requires. It's better that the test overrides user provided options than fail due to incompatible configuration. It makes maintenance of the tests much easier because we don't have to declare and maintain the supported list of user options for every test. Either the test works for all configurations (i.e. whatever the user sets in MKFS/MOUNT_OPTIONS), or it specifically defines the configuration it is testing. 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
