summaryrefslogtreecommitdiffstats
path: root/mm/kmemleak-test.c
diff options
context:
space:
mode:
authorLuis R. Rodriguez <mcgrof@kernel.org>2018-03-10 06:14:54 -0800
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2018-03-20 09:28:47 +0100
commitb3cf21fae1fe0b3a3e8ada0a60d3fb6217ebce5b (patch)
tree596001ec72a41c279e5f0c055a2a2f87f357c364 /mm/kmemleak-test.c
parentf5a614519e67b429faf01ca36db90030976449cc (diff)
downloadlinux-b3cf21fae1fe0b3a3e8ada0a60d3fb6217ebce5b.tar.gz
linux-b3cf21fae1fe0b3a3e8ada0a60d3fb6217ebce5b.tar.bz2
linux-b3cf21fae1fe0b3a3e8ada0a60d3fb6217ebce5b.zip
test_firmware: test three firmware kernel configs using a proc knob
Since we now have knobs to twiddle what used to be set on kernel configurations we can build one base kernel configuration and modify behaviour to mimic such kernel configurations to test them. Provided you build a kernel with: CONFIG_TEST_FIRMWARE=y CONFIG_FW_LOADER=y CONFIG_FW_LOADER_USER_HELPER=y CONFIG_IKCONFIG=y CONFIG_IKCONFIG_PROC=y We should now be able test all possible kernel configurations when FW_LOADER=y. Note that when FW_LOADER=m we just don't provide the built-in functionality of the built-in firmware. If you're on an old kernel and either don't have /proc/config.gz (CONFIG_IKCONFIG_PROC) or haven't enabled CONFIG_FW_LOADER_USER_HELPER we cannot run these dynamic tests, so just run both scripts just as we used to before making blunt assumptions about your setup and requirements exactly as we did before. Acked-by: Kees Cook <keescook@chromium.org> Signed-off-by: Luis R. Rodriguez <mcgrof@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'mm/kmemleak-test.c')
0 files changed, 0 insertions, 0 deletions