On Fri, Apr 18, 2025 at 01:50:47PM -0300, Herton R. Krzesinski wrote: > Right now test_kmod has hardcoded dependencies on btrfs/xfs. That > is not optimal since you end up needing to select/build them, but it > is not really required since other fs could be selected for the testing. > Also, we can't change the default/driver module used for testing on > initialization. > > Thus make it more generic: introduce two module parameters (start_driver > and start_test_fs), which allow to select which modules/fs to use for > the testing on test_kmod initialization. Then it's up to the user to > select which modules/fs to use for testing based on his config. However, > keep test_module as required default. > > This way, config/modules becomes selectable as when the testing is done > from selftests (userspace). > > While at it, also change trigger_config_run_type, since at module > initialization we already set the defaults at __kmod_config_init and > should not need to do it again in test_kmod_init(), thus we can > avoid to again set test_driver/test_fs. > > v2: also update tools/testing/selftests/kmod/config with the removed > dependencies. > > Signed-off-by: Herton R. Krzesinski <her...@redhat.com>
Reviewed-by: Luis Chambelrain <mcg...@kernel.org> Luis
