On Thu, Jul 17, 2014 at 6:47 PM, Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > On Mon, Jul 14, 2014 at 02:38:12PM -0700, Kees Cook wrote: >> This provides a simple interface to trigger the firmware_class loader >> to test built-in, filesystem, and user helper modes. Additionally adds >> tests via the new interface to the selftests tree. >> >> Signed-off-by: Kees Cook <keescook@xxxxxxxxxxxx> >> --- >> lib/Kconfig.debug | 13 +++ >> lib/Makefile | 1 + >> lib/test_firmware.c | 117 +++++++++++++++++++++ > > Side note, I find it odd that in-kernel test modules are in lib/. > > But whatever, you aren't the one that did this first, so I'm not going > to object here, I'll apply this, nice work. Yeah, with each new selftest, I become less and less happy with the lack of an intentional layout and execution framework. I've been pondering some ideas on cleaning it up, but I have nothing solid yet. The main reason for things living lib/ is because of how the Kconfig.debug stuff is layed out. I think separating the concept of "debug" from "test" is needed, and then the selftests make targets need to be sorted out so that there's some common reporting method of success vs failure, and that failures don't abort the whole thing, etc, etc. -Kees -- Kees Cook Chrome OS Security -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
