ktest.pl minconfig: Unset configs instead of just removing them
authorSteven Rostedt <rostedt@goodmis.org>
Fri, 2 Dec 2022 16:59:36 +0000 (11:59 -0500)
committerSteven Rostedt (Google) <rostedt@goodmis.org>
Thu, 8 Dec 2022 01:36:16 +0000 (20:36 -0500)
commitef784eebb56425eed6e9b16e7d47e5c00dcf9c38
treea59399b99c68d8d86b844d039a2d7111ccc1f88a
parent76dcd734eca23168cb008912c0f69ff408905235
ktest.pl minconfig: Unset configs instead of just removing them

After a full run of a make_min_config test, I noticed there were a lot of
CONFIGs still enabled that really should not be. Looking at them, I
noticed they were all defined as "default y". The issue is that the test
simple removes the config and re-runs make oldconfig, which enables it
again because it is set to default 'y'. Instead, explicitly disable the
config with writing "# CONFIG_FOO is not set" to the file to keep it from
being set again.

With this change, one of my box's minconfigs went from 768 configs set,
down to 521 configs set.

Link: https://lkml.kernel.org/r/20221202115936.016fce23@gandalf.local.home
Cc: stable@vger.kernel.org
Fixes: 0a05c769a9de5 ("ktest: Added config_bisect test type")
Reviewed-by: John 'Warthog9' Hawley (VMware) <warthog9@eaglescrag.net>
Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
tools/testing/ktest/ktest.pl