2017-05-26 11:44:00 -07:00
|
|
|
======================
|
2013-02-27 18:05:57 -07:00
|
|
|
Linux Kernel Selftests
|
2017-05-26 11:44:00 -07:00
|
|
|
======================
|
2013-02-27 18:05:57 -07:00
|
|
|
|
|
|
|
The kernel contains a set of "self tests" under the tools/testing/selftests/
|
2016-08-18 02:36:53 -07:00
|
|
|
directory. These are intended to be small tests to exercise individual code
|
|
|
|
paths in the kernel. Tests are intended to be run after building, installing
|
|
|
|
and booting a kernel.
|
2013-02-27 18:05:57 -07:00
|
|
|
|
2022-01-26 13:13:41 -07:00
|
|
|
Kselftest from mainline can be run on older stable kernels. Running tests
|
|
|
|
from mainline offers the best coverage. Several test rings run mainline
|
|
|
|
kselftest suite on stable releases. The reason is that when a new test
|
|
|
|
gets added to test existing code to regression test a bug, we should be
|
|
|
|
able to run that test on an older kernel. Hence, it is important to keep
|
|
|
|
code that can still test an older kernel and make sure it skips the test
|
|
|
|
gracefully on newer releases.
|
|
|
|
|
2019-04-17 16:34:03 -07:00
|
|
|
You can find additional information on Kselftest framework, how to
|
|
|
|
write new tests using the framework on Kselftest wiki:
|
|
|
|
|
|
|
|
https://kselftest.wiki.kernel.org/
|
|
|
|
|
2014-07-02 08:51:38 -07:00
|
|
|
On some systems, hot-plug tests could hang forever waiting for cpu and
|
|
|
|
memory to be ready to be offlined. A special hot-plug target is created
|
2018-11-04 15:06:23 -07:00
|
|
|
to run the full range of hot-plug tests. In default mode, hot-plug tests run
|
2014-07-02 08:51:38 -07:00
|
|
|
in safe mode with a limited scope. In limited mode, cpu-hotplug test is
|
|
|
|
run on a single cpu as opposed to all hotplug capable cpus, and memory
|
|
|
|
hotplug test is run on 2% of hotplug capable memory instead of 10%.
|
|
|
|
|
2019-04-04 18:58:56 -07:00
|
|
|
kselftest runs as a userspace process. Tests that can be written/run in
|
|
|
|
userspace may wish to use the `Test Harness`_. Tests that need to be
|
|
|
|
run in kernel space may wish to use a `Test Module`_.
|
|
|
|
|
2014-07-02 08:51:38 -07:00
|
|
|
Running the selftests (hotplug tests are run in limited mode)
|
|
|
|
=============================================================
|
2013-02-27 18:05:57 -07:00
|
|
|
|
2017-05-26 11:44:00 -07:00
|
|
|
To build the tests::
|
|
|
|
|
2023-06-06 00:16:36 -07:00
|
|
|
$ make headers
|
2017-06-17 08:26:40 -07:00
|
|
|
$ make -C tools/testing/selftests
|
2017-05-26 11:44:00 -07:00
|
|
|
|
|
|
|
To run the tests::
|
2013-02-27 18:05:57 -07:00
|
|
|
|
2017-06-17 08:26:40 -07:00
|
|
|
$ make -C tools/testing/selftests run_tests
|
2013-02-27 18:05:57 -07:00
|
|
|
|
2017-05-26 11:44:00 -07:00
|
|
|
To build and run the tests with a single command, use::
|
2013-02-27 18:05:57 -07:00
|
|
|
|
2017-06-17 08:26:40 -07:00
|
|
|
$ make kselftest
|
2014-11-19 17:16:16 -07:00
|
|
|
|
2017-05-26 11:44:00 -07:00
|
|
|
Note that some tests will require root privileges.
|
2013-02-27 18:05:57 -07:00
|
|
|
|
2019-04-17 16:34:03 -07:00
|
|
|
Kselftest supports saving output files in a separate directory and then
|
|
|
|
running tests. To locate output files in a separate directory two syntaxes
|
|
|
|
are supported. In both cases the working directory must be the root of the
|
|
|
|
kernel src. This is applicable to "Running a subset of selftests" section
|
|
|
|
below.
|
|
|
|
|
|
|
|
To build, save output files in a separate directory with O= ::
|
2017-10-02 16:44:17 -07:00
|
|
|
|
|
|
|
$ make O=/tmp/kselftest kselftest
|
|
|
|
|
2019-04-17 16:34:03 -07:00
|
|
|
To build, save output files in a separate directory with KBUILD_OUTPUT ::
|
|
|
|
|
|
|
|
$ export KBUILD_OUTPUT=/tmp/kselftest; make kselftest
|
2017-10-02 16:44:17 -07:00
|
|
|
|
2019-04-17 16:34:03 -07:00
|
|
|
The O= assignment takes precedence over the KBUILD_OUTPUT environment
|
|
|
|
variable.
|
2017-10-02 16:44:17 -07:00
|
|
|
|
2019-04-17 16:34:03 -07:00
|
|
|
The above commands by default run the tests and print full pass/fail report.
|
|
|
|
Kselftest supports "summary" option to make it easier to understand the test
|
|
|
|
results. Please find the detailed individual test results for each test in
|
|
|
|
/tmp/testname file(s) when summary option is specified. This is applicable
|
|
|
|
to "Running a subset of selftests" section below.
|
|
|
|
|
|
|
|
To run kselftest with summary option enabled ::
|
|
|
|
|
|
|
|
$ make summary=1 kselftest
|
2013-02-27 18:05:57 -07:00
|
|
|
|
2014-11-19 17:16:16 -07:00
|
|
|
Running a subset of selftests
|
2017-05-26 11:44:00 -07:00
|
|
|
=============================
|
|
|
|
|
2014-11-19 17:16:16 -07:00
|
|
|
You can use the "TARGETS" variable on the make command line to specify
|
|
|
|
single test to run, or a list of tests to run.
|
|
|
|
|
2017-05-26 11:44:00 -07:00
|
|
|
To run only tests targeted for a single subsystem::
|
|
|
|
|
2017-06-17 08:26:40 -07:00
|
|
|
$ make -C tools/testing/selftests TARGETS=ptrace run_tests
|
2014-11-19 17:16:16 -07:00
|
|
|
|
2017-05-26 11:44:00 -07:00
|
|
|
You can specify multiple tests to build and run::
|
|
|
|
|
2017-06-17 08:26:40 -07:00
|
|
|
$ make TARGETS="size timers" kselftest
|
2014-11-19 17:16:16 -07:00
|
|
|
|
2019-04-17 16:34:03 -07:00
|
|
|
To build, save output files in a separate directory with O= ::
|
2017-10-02 16:44:17 -07:00
|
|
|
|
|
|
|
$ make O=/tmp/kselftest TARGETS="size timers" kselftest
|
|
|
|
|
2019-04-17 16:34:03 -07:00
|
|
|
To build, save output files in a separate directory with KBUILD_OUTPUT ::
|
2017-10-02 16:44:17 -07:00
|
|
|
|
2019-04-17 16:34:03 -07:00
|
|
|
$ export KBUILD_OUTPUT=/tmp/kselftest; make TARGETS="size timers" kselftest
|
2017-10-02 16:44:17 -07:00
|
|
|
|
2019-09-26 10:52:18 -07:00
|
|
|
Additionally you can use the "SKIP_TARGETS" variable on the make command
|
|
|
|
line to specify one or more targets to exclude from the TARGETS list.
|
|
|
|
|
|
|
|
To run all tests but a single subsystem::
|
|
|
|
|
|
|
|
$ make -C tools/testing/selftests SKIP_TARGETS=ptrace run_tests
|
|
|
|
|
|
|
|
You can specify multiple tests to skip::
|
|
|
|
|
|
|
|
$ make SKIP_TARGETS="size timers" kselftest
|
|
|
|
|
|
|
|
You can also specify a restricted list of tests to run together with a
|
|
|
|
dedicated skiplist::
|
|
|
|
|
2023-10-09 08:09:29 -07:00
|
|
|
$ make TARGETS="breakpoints size timers" SKIP_TARGETS=size kselftest
|
2019-09-26 10:52:18 -07:00
|
|
|
|
2014-11-19 17:16:16 -07:00
|
|
|
See the top-level tools/testing/selftests/Makefile for the list of all
|
|
|
|
possible targets.
|
2013-02-27 18:05:57 -07:00
|
|
|
|
2014-07-02 08:51:38 -07:00
|
|
|
Running the full range hotplug selftests
|
|
|
|
========================================
|
|
|
|
|
2017-05-26 11:44:00 -07:00
|
|
|
To build the hotplug tests::
|
|
|
|
|
2017-06-17 08:26:40 -07:00
|
|
|
$ make -C tools/testing/selftests hotplug
|
2017-05-26 11:44:00 -07:00
|
|
|
|
|
|
|
To run the hotplug tests::
|
2014-07-02 08:51:38 -07:00
|
|
|
|
2017-06-17 08:26:40 -07:00
|
|
|
$ make -C tools/testing/selftests run_hotplug
|
2014-07-02 08:51:38 -07:00
|
|
|
|
2017-05-26 11:44:00 -07:00
|
|
|
Note that some tests will require root privileges.
|
2013-02-27 18:05:57 -07:00
|
|
|
|
2014-11-19 17:16:16 -07:00
|
|
|
|
2015-09-23 02:35:25 -07:00
|
|
|
Install selftests
|
|
|
|
=================
|
|
|
|
|
2020-09-28 13:26:50 -07:00
|
|
|
You can use the "install" target of "make" (which calls the `kselftest_install.sh`
|
|
|
|
tool) to install selftests in the default location (`tools/testing/selftests/kselftest_install`),
|
|
|
|
or in a user specified location via the `INSTALL_PATH` "make" variable.
|
2015-09-23 02:35:25 -07:00
|
|
|
|
2017-05-26 11:44:00 -07:00
|
|
|
To install selftests in default location::
|
2015-09-23 02:35:25 -07:00
|
|
|
|
2020-09-28 13:26:50 -07:00
|
|
|
$ make -C tools/testing/selftests install
|
2017-05-26 11:44:00 -07:00
|
|
|
|
|
|
|
To install selftests in a user specified location::
|
|
|
|
|
2020-09-28 13:26:50 -07:00
|
|
|
$ make -C tools/testing/selftests install INSTALL_PATH=/some/other/path
|
2015-09-23 02:35:25 -07:00
|
|
|
|
2016-11-07 13:24:14 -07:00
|
|
|
Running installed selftests
|
|
|
|
===========================
|
|
|
|
|
2020-09-28 13:26:50 -07:00
|
|
|
Found in the install directory, as well as in the Kselftest tarball,
|
|
|
|
is a script named `run_kselftest.sh` to run the tests.
|
2016-11-07 13:24:14 -07:00
|
|
|
|
2018-11-04 15:06:23 -07:00
|
|
|
You can simply do the following to run the installed Kselftests. Please
|
2017-06-17 08:26:40 -07:00
|
|
|
note some tests will require root privileges::
|
2016-11-07 13:24:14 -07:00
|
|
|
|
2020-09-28 13:26:50 -07:00
|
|
|
$ cd kselftest_install
|
2017-06-17 08:26:40 -07:00
|
|
|
$ ./run_kselftest.sh
|
2015-09-23 02:35:25 -07:00
|
|
|
|
2020-09-28 13:26:50 -07:00
|
|
|
To see the list of available tests, the `-l` option can be used::
|
|
|
|
|
|
|
|
$ ./run_kselftest.sh -l
|
|
|
|
|
|
|
|
The `-c` option can be used to run all the tests from a test collection, or
|
|
|
|
the `-t` option for specific single tests. Either can be used multiple times::
|
|
|
|
|
2023-10-09 08:09:29 -07:00
|
|
|
$ ./run_kselftest.sh -c size -c seccomp -t timers:posix_timers -t timer:nanosleep
|
2020-09-28 13:26:50 -07:00
|
|
|
|
|
|
|
For other features see the script usage output, seen with the `-h` option.
|
|
|
|
|
2023-04-14 12:38:45 -07:00
|
|
|
Timeout for selftests
|
|
|
|
=====================
|
|
|
|
|
|
|
|
Selftests are designed to be quick and so a default timeout is used of 45
|
|
|
|
seconds for each test. Tests can override the default timeout by adding
|
|
|
|
a settings file in their directory and set a timeout variable there to the
|
|
|
|
configured a desired upper timeout for the test. Only a few tests override
|
|
|
|
the timeout with a value higher than 45 seconds, selftests strives to keep
|
|
|
|
it that way. Timeouts in selftests are not considered fatal because the
|
|
|
|
system under which a test runs may change and this can also modify the
|
|
|
|
expected time it takes to run a test. If you have control over the systems
|
|
|
|
which will run the tests you can configure a test runner on those systems to
|
|
|
|
use a greater or lower timeout on the command line as with the `-o` or
|
|
|
|
the `--override-timeout` argument. For example to use 165 seconds instead
|
2024-04-29 09:50:47 -07:00
|
|
|
one would use::
|
2023-04-14 12:38:45 -07:00
|
|
|
|
|
|
|
$ ./run_kselftest.sh --override-timeout 165
|
|
|
|
|
|
|
|
You can look at the TAP output to see if you ran into the timeout. Test
|
|
|
|
runners which know a test must run under a specific time can then optionally
|
|
|
|
treat these timeouts then as fatal.
|
|
|
|
|
2020-05-19 13:00:45 -07:00
|
|
|
Packaging selftests
|
|
|
|
===================
|
|
|
|
|
|
|
|
In some cases packaging is desired, such as when tests need to run on a
|
|
|
|
different system. To package selftests, run::
|
|
|
|
|
|
|
|
$ make -C tools/testing/selftests gen_tar
|
|
|
|
|
|
|
|
This generates a tarball in the `INSTALL_PATH/kselftest-packages` directory. By
|
2020-09-28 13:26:50 -07:00
|
|
|
default, `.gz` format is used. The tar compression format can be overridden by
|
|
|
|
specifying a `FORMAT` make variable. Any value recognized by `tar's auto-compress`_
|
|
|
|
option is supported, such as::
|
2020-05-19 13:00:45 -07:00
|
|
|
|
|
|
|
$ make -C tools/testing/selftests gen_tar FORMAT=.xz
|
|
|
|
|
|
|
|
`make gen_tar` invokes `make install` so you can use it to package a subset of
|
|
|
|
tests by using variables specified in `Running a subset of selftests`_
|
|
|
|
section::
|
|
|
|
|
2023-10-09 08:09:29 -07:00
|
|
|
$ make -C tools/testing/selftests gen_tar TARGETS="size" FORMAT=.xz
|
2020-05-19 13:00:45 -07:00
|
|
|
|
|
|
|
.. _tar's auto-compress: https://www.gnu.org/software/tar/manual/html_node/gzip.html#auto_002dcompress
|
|
|
|
|
2013-02-27 18:05:57 -07:00
|
|
|
Contributing new tests
|
|
|
|
======================
|
|
|
|
|
2016-02-23 09:08:11 -07:00
|
|
|
In general, the rules for selftests are
|
2013-02-27 18:05:57 -07:00
|
|
|
|
|
|
|
* Do as much as you can if you're not root;
|
|
|
|
|
|
|
|
* Don't take too long;
|
|
|
|
|
|
|
|
* Don't break the build on any architecture, and
|
|
|
|
|
|
|
|
* Don't cause the top-level "make run_tests" to fail if your feature is
|
|
|
|
unconfigured.
|
2016-11-29 04:55:47 -07:00
|
|
|
|
2024-06-12 00:27:23 -07:00
|
|
|
* The output of tests must conform to the TAP standard to ensure high
|
|
|
|
testing quality and to capture failures/errors with specific details.
|
|
|
|
The kselftest.h and kselftest_harness.h headers provide wrappers for
|
|
|
|
outputting test results. These wrappers should be used for pass,
|
|
|
|
fail, exit, and skip messages. CI systems can easily parse TAP output
|
|
|
|
messages to detect test results.
|
|
|
|
|
2017-05-26 11:44:00 -07:00
|
|
|
Contributing new tests (details)
|
|
|
|
================================
|
2016-11-29 04:55:47 -07:00
|
|
|
|
2022-05-21 00:36:51 -07:00
|
|
|
* In your Makefile, use facilities from lib.mk by including it instead of
|
|
|
|
reinventing the wheel. Specify flags and binaries generation flags on
|
|
|
|
need basis before including lib.mk. ::
|
|
|
|
|
|
|
|
CFLAGS = $(KHDR_INCLUDES)
|
|
|
|
TEST_GEN_PROGS := close_range_test
|
|
|
|
include ../lib.mk
|
|
|
|
|
2016-11-29 04:55:47 -07:00
|
|
|
* Use TEST_GEN_XXX if such binaries or files are generated during
|
|
|
|
compiling.
|
2017-06-17 08:26:40 -07:00
|
|
|
|
2017-10-02 16:44:17 -07:00
|
|
|
TEST_PROGS, TEST_GEN_PROGS mean it is the executable tested by
|
2016-11-29 04:55:47 -07:00
|
|
|
default.
|
2017-06-17 08:26:40 -07:00
|
|
|
|
2024-01-12 10:43:50 -07:00
|
|
|
TEST_GEN_MODS_DIR should be used by tests that require modules to be built
|
|
|
|
before the test starts. The variable will contain the name of the directory
|
|
|
|
containing the modules.
|
|
|
|
|
2017-10-02 16:44:17 -07:00
|
|
|
TEST_CUSTOM_PROGS should be used by tests that require custom build
|
2018-11-04 15:06:23 -07:00
|
|
|
rules and prevent common build rule use.
|
2017-10-02 16:44:17 -07:00
|
|
|
|
|
|
|
TEST_PROGS are for test shell scripts. Please ensure shell script has
|
|
|
|
its exec bit set. Otherwise, lib.mk run_tests will generate a warning.
|
|
|
|
|
|
|
|
TEST_CUSTOM_PROGS and TEST_PROGS will be run by common run_tests.
|
|
|
|
|
2016-11-29 04:55:47 -07:00
|
|
|
TEST_PROGS_EXTENDED, TEST_GEN_PROGS_EXTENDED mean it is the
|
|
|
|
executable which is not tested by default.
|
2024-01-26 16:21:18 -07:00
|
|
|
|
2016-11-29 04:55:47 -07:00
|
|
|
TEST_FILES, TEST_GEN_FILES mean it is the file which is used by
|
|
|
|
test.
|
2017-06-05 11:37:17 -07:00
|
|
|
|
2024-01-26 16:21:18 -07:00
|
|
|
TEST_INCLUDES is similar to TEST_FILES, it lists files which should be
|
|
|
|
included when exporting or installing the tests, with the following
|
|
|
|
differences:
|
|
|
|
|
|
|
|
* symlinks to files in other directories are preserved
|
|
|
|
* the part of paths below tools/testing/selftests/ is preserved when
|
|
|
|
copying the files to the output directory
|
|
|
|
|
|
|
|
TEST_INCLUDES is meant to list dependencies located in other directories of
|
|
|
|
the selftests hierarchy.
|
|
|
|
|
2018-04-19 03:28:25 -07:00
|
|
|
* First use the headers inside the kernel source and/or git repo, and then the
|
|
|
|
system headers. Headers for the kernel release as opposed to headers
|
|
|
|
installed by the distro on the system should be the primary focus to be able
|
2022-05-21 00:36:51 -07:00
|
|
|
to find regressions. Use KHDR_INCLUDES in Makefile to include headers from
|
|
|
|
the kernel source.
|
2018-04-19 03:28:25 -07:00
|
|
|
|
2018-06-29 05:52:01 -07:00
|
|
|
* If a test needs specific kernel config options enabled, add a config file in
|
|
|
|
the test directory to enable them.
|
|
|
|
|
2018-08-24 05:47:44 -07:00
|
|
|
e.g: tools/testing/selftests/android/config
|
2018-06-29 05:52:01 -07:00
|
|
|
|
2022-05-21 00:36:51 -07:00
|
|
|
* Create a .gitignore file inside test directory and add all generated objects
|
|
|
|
in it.
|
|
|
|
|
|
|
|
* Add new test name in TARGETS in selftests/Makefile::
|
|
|
|
|
|
|
|
TARGETS += android
|
|
|
|
|
|
|
|
* All changes should pass::
|
|
|
|
|
|
|
|
kselftest-{all,install,clean,gen_tar}
|
|
|
|
kselftest-{all,install,clean,gen_tar} O=abo_path
|
|
|
|
kselftest-{all,install,clean,gen_tar} O=rel_path
|
|
|
|
make -C tools/testing/selftests {all,install,clean,gen_tar}
|
|
|
|
make -C tools/testing/selftests {all,install,clean,gen_tar} O=abs_path
|
|
|
|
make -C tools/testing/selftests {all,install,clean,gen_tar} O=rel_path
|
|
|
|
|
2019-04-04 18:58:56 -07:00
|
|
|
Test Module
|
|
|
|
===========
|
|
|
|
|
|
|
|
Kselftest tests the kernel from userspace. Sometimes things need
|
|
|
|
testing from within the kernel, one method of doing this is to create a
|
|
|
|
test module. We can tie the module into the kselftest framework by
|
2019-12-05 20:17:38 -07:00
|
|
|
using a shell script test runner. ``kselftest/module.sh`` is designed
|
2019-04-04 18:58:56 -07:00
|
|
|
to facilitate this process. There is also a header file provided to
|
|
|
|
assist writing kernel modules that are for use with kselftest:
|
|
|
|
|
2021-02-24 06:06:05 -07:00
|
|
|
- ``tools/testing/selftests/kselftest_module.h``
|
|
|
|
- ``tools/testing/selftests/kselftest/module.sh``
|
2019-04-04 18:58:56 -07:00
|
|
|
|
selftest: Taint kernel when test module loaded
Make any kselftest test module (using the kselftest_module framework)
taint the kernel with TAINT_TEST on module load.
Also mark the module as a test module using MODULE_INFO(test, "Y") so
that other tools can tell this is a test module. We can't rely solely
on this, though, as these test modules are also often built-in.
Finally, update the kselftest documentation to mention that the kernel
should be tainted, and how to do so manually (as below).
Note that several selftests use kernel modules which are not based on
the kselftest_module framework, and so will not automatically taint the
kernel.
This can be done in two ways:
- Moving the module to the tools/testing directory. All modules under
this directory will taint the kernel.
- Adding the 'test' module property with:
MODULE_INFO(test, "Y")
Similarly, selftests which do not load modules into the kernel generally
should not taint the kernel (or possibly should only do so on failure),
as it's assumed that testing from user-space should be safe. Regardless,
they can write to /proc/sys/kernel/tainted if required.
Reviewed-by: Luis Chamberlain <mcgrof@kernel.org>
Acked-by: Brendan Higgins <brendanhiggins@google.com>
Signed-off-by: David Gow <davidgow@google.com>
Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
2022-07-07 21:48:47 -07:00
|
|
|
Note that test modules should taint the kernel with TAINT_TEST. This will
|
|
|
|
happen automatically for modules which are in the ``tools/testing/``
|
|
|
|
directory, or for modules which use the ``kselftest_module.h`` header above.
|
|
|
|
Otherwise, you'll need to add ``MODULE_INFO(test, "Y")`` to your module
|
|
|
|
source. selftests which do not load modules typically should not taint the
|
|
|
|
kernel, but in cases where a non-test module is loaded, TEST_TAINT can be
|
|
|
|
applied from userspace by writing to ``/proc/sys/kernel/tainted``.
|
|
|
|
|
2019-04-04 18:58:56 -07:00
|
|
|
How to use
|
|
|
|
----------
|
|
|
|
|
|
|
|
Here we show the typical steps to create a test module and tie it into
|
|
|
|
kselftest. We use kselftests for lib/ as an example.
|
|
|
|
|
|
|
|
1. Create the test module
|
|
|
|
|
|
|
|
2. Create the test script that will run (load/unload) the module
|
|
|
|
e.g. ``tools/testing/selftests/lib/printf.sh``
|
|
|
|
|
|
|
|
3. Add line to config file e.g. ``tools/testing/selftests/lib/config``
|
|
|
|
|
|
|
|
4. Add test script to makefile e.g. ``tools/testing/selftests/lib/Makefile``
|
|
|
|
|
|
|
|
5. Verify it works:
|
|
|
|
|
|
|
|
.. code-block:: sh
|
|
|
|
|
|
|
|
# Assumes you have booted a fresh build of this kernel tree
|
|
|
|
cd /path/to/linux/tree
|
|
|
|
make kselftest-merge
|
|
|
|
make modules
|
|
|
|
sudo make modules_install
|
|
|
|
make TARGETS=lib kselftest
|
|
|
|
|
|
|
|
Example Module
|
|
|
|
--------------
|
|
|
|
|
|
|
|
A bare bones test module might look like this:
|
|
|
|
|
|
|
|
.. code-block:: c
|
|
|
|
|
|
|
|
// SPDX-License-Identifier: GPL-2.0+
|
|
|
|
|
|
|
|
#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
|
|
|
|
|
2022-08-24 07:25:05 -07:00
|
|
|
#include "../tools/testing/selftests/kselftest_module.h"
|
2019-04-04 18:58:56 -07:00
|
|
|
|
|
|
|
KSTM_MODULE_GLOBALS();
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Kernel module for testing the foobinator
|
|
|
|
*/
|
|
|
|
|
|
|
|
static int __init test_function()
|
|
|
|
{
|
|
|
|
...
|
|
|
|
}
|
|
|
|
|
|
|
|
static void __init selftest(void)
|
|
|
|
{
|
|
|
|
KSTM_CHECK_ZERO(do_test_case("", 0));
|
|
|
|
}
|
|
|
|
|
|
|
|
KSTM_MODULE_LOADERS(test_foo);
|
|
|
|
MODULE_AUTHOR("John Developer <jd@fooman.org>");
|
|
|
|
MODULE_LICENSE("GPL");
|
selftest: Taint kernel when test module loaded
Make any kselftest test module (using the kselftest_module framework)
taint the kernel with TAINT_TEST on module load.
Also mark the module as a test module using MODULE_INFO(test, "Y") so
that other tools can tell this is a test module. We can't rely solely
on this, though, as these test modules are also often built-in.
Finally, update the kselftest documentation to mention that the kernel
should be tainted, and how to do so manually (as below).
Note that several selftests use kernel modules which are not based on
the kselftest_module framework, and so will not automatically taint the
kernel.
This can be done in two ways:
- Moving the module to the tools/testing directory. All modules under
this directory will taint the kernel.
- Adding the 'test' module property with:
MODULE_INFO(test, "Y")
Similarly, selftests which do not load modules into the kernel generally
should not taint the kernel (or possibly should only do so on failure),
as it's assumed that testing from user-space should be safe. Regardless,
they can write to /proc/sys/kernel/tainted if required.
Reviewed-by: Luis Chamberlain <mcgrof@kernel.org>
Acked-by: Brendan Higgins <brendanhiggins@google.com>
Signed-off-by: David Gow <davidgow@google.com>
Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
2022-07-07 21:48:47 -07:00
|
|
|
MODULE_INFO(test, "Y");
|
2019-04-04 18:58:56 -07:00
|
|
|
|
|
|
|
Example test script
|
|
|
|
-------------------
|
|
|
|
|
|
|
|
.. code-block:: sh
|
|
|
|
|
|
|
|
#!/bin/bash
|
|
|
|
# SPDX-License-Identifier: GPL-2.0+
|
2019-12-05 20:17:38 -07:00
|
|
|
$(dirname $0)/../kselftest/module.sh "foo" test_foo
|
2019-04-04 18:58:56 -07:00
|
|
|
|
|
|
|
|
2017-06-05 11:37:17 -07:00
|
|
|
Test Harness
|
|
|
|
============
|
|
|
|
|
2019-04-04 18:58:56 -07:00
|
|
|
The kselftest_harness.h file contains useful helpers to build tests. The
|
|
|
|
test harness is for userspace testing, for kernel space testing see `Test
|
|
|
|
Module`_ above.
|
|
|
|
|
|
|
|
The tests from tools/testing/selftests/seccomp/seccomp_bpf.c can be used as
|
|
|
|
example.
|
2017-06-05 11:37:17 -07:00
|
|
|
|
|
|
|
Example
|
|
|
|
-------
|
|
|
|
|
|
|
|
.. kernel-doc:: tools/testing/selftests/kselftest_harness.h
|
|
|
|
:doc: example
|
|
|
|
|
|
|
|
|
|
|
|
Helpers
|
|
|
|
-------
|
|
|
|
|
|
|
|
.. kernel-doc:: tools/testing/selftests/kselftest_harness.h
|
|
|
|
:functions: TH_LOG TEST TEST_SIGNAL FIXTURE FIXTURE_DATA FIXTURE_SETUP
|
2020-04-27 18:03:50 -07:00
|
|
|
FIXTURE_TEARDOWN TEST_F TEST_HARNESS_MAIN FIXTURE_VARIANT
|
|
|
|
FIXTURE_VARIANT_ADD
|
2017-06-05 11:37:17 -07:00
|
|
|
|
|
|
|
Operators
|
|
|
|
---------
|
|
|
|
|
|
|
|
.. kernel-doc:: tools/testing/selftests/kselftest_harness.h
|
|
|
|
:doc: operators
|
|
|
|
|
|
|
|
.. kernel-doc:: tools/testing/selftests/kselftest_harness.h
|
|
|
|
:functions: ASSERT_EQ ASSERT_NE ASSERT_LT ASSERT_LE ASSERT_GT ASSERT_GE
|
|
|
|
ASSERT_NULL ASSERT_TRUE ASSERT_NULL ASSERT_TRUE ASSERT_FALSE
|
|
|
|
ASSERT_STREQ ASSERT_STRNE EXPECT_EQ EXPECT_NE EXPECT_LT
|
|
|
|
EXPECT_LE EXPECT_GT EXPECT_GE EXPECT_NULL EXPECT_TRUE
|
|
|
|
EXPECT_FALSE EXPECT_STREQ EXPECT_STRNE
|