Normalize it before adding the blacklist. Without normalizing it we
have, with just the test addition:
$ ./build/testsuite/test-modprobe modprobe_param_kcmdline9
TESTSUITE: running modprobe_param_kcmdline9, in forked context
TESTSUITE: ERR: Outputs do not match on STDOUT:
TESTSUITE: ERR: correct:
...
blacklist foo_bar
...
TESTSUITE: ERR: wrong:
blacklist foo-bar
TESTSUITE: ERR: FAILED: exit ok but outputs do not match: modprobe_param_kcmdline9
Link: https://github.com/kmod-project/kmod/pull/312
Signed-off-by: Lucas De Marchi <demarchi@kernel.org>
if (t == NULL)
break;
+ if (underscores(t) < 0)
+ continue;
+
kmod_config_add_blacklist(config, t);
}
} else {
blacklist foo2
blacklist bar2
blacklist foobar
+blacklist foo_bar
# End of configuration files. Dumping indexes now:
-modprobe.blacklist=foo,bar modprobe.blacklist=foo2 quiet modprobe.blacklist=bar2 rw modprobe.blacklist=foobar
+modprobe.blacklist=foo,bar modprobe.blacklist=foo2 quiet modprobe.blacklist=bar2 rw modprobe.blacklist=foobar modprobe.blacklist=foo-bar