module: kunit: Load .kunit_test_suites section when CONFIG_KUNIT=m
The new KUnit module handling has KUnit test suites listed in a
.kunit_test_suites section of each module. This should be loaded when
the module is, but at the moment this only happens if KUnit is built-in.
Also load this when KUnit is enabled as a module: it'll not be usable
unless KUnit is loaded, but such modules are likely to depend on KUnit
anyway, so it's unlikely to ever be loaded needlessly.
Fixes: 3d6e446238
("kunit: unify module and builtin suite definitions")
Signed-off-by: David Gow <davidgow@google.com>
Reviewed-by: Brendan Higgins <brendanhiggins@google.com>
Tested-by: Geert Uytterhoeven <geert@linux-m68k.org>
Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
This commit is contained in:
parent
d52788b3da
commit
41a55567b9
|
@ -2099,7 +2099,7 @@ static int find_module_sections(struct module *mod, struct load_info *info)
|
||||||
sizeof(*mod->static_call_sites),
|
sizeof(*mod->static_call_sites),
|
||||||
&mod->num_static_call_sites);
|
&mod->num_static_call_sites);
|
||||||
#endif
|
#endif
|
||||||
#ifdef CONFIG_KUNIT
|
#if IS_ENABLED(CONFIG_KUNIT)
|
||||||
mod->kunit_suites = section_objs(info, ".kunit_test_suites",
|
mod->kunit_suites = section_objs(info, ".kunit_test_suites",
|
||||||
sizeof(*mod->kunit_suites),
|
sizeof(*mod->kunit_suites),
|
||||||
&mod->num_kunit_suites);
|
&mod->num_kunit_suites);
|
||||||
|
|
Loading…
Reference in New Issue