On Thu, Nov 28, 2024 at 03:10:34PM +0100, Geert Uytterhoeven wrote: > Despite the warning, I gave this a try on m68k (cross-compiled on i7 ;-). > However, I didn't notice any extra-ordinary build times. I had some large values before this got merged and due to this slowing down builds 2x I reduced the defaults. The current defaults are no known as TEST_KALLSYMS_LARGE. > Also, when running the test manually on ARAnyM, everything runs > in the blink of an eye. I didn't use the script, but ran all commands > manually. I tried insmodding a/b/c/d, c/a/b, a/c/d/b. > > Is this expected? I tried to clarify the ranges known we can use to mess with this test a bit more in the recent fixes on modules-next [0] so since you want to see some things blow up try TEST_KALLSYMS_MAX, on some systems this is reported to crash the build. It is why I had reduced the original values a bit... [0] git://git.kernel.org/pub/scm/linux/kernel/git/modules/linux.git modules-next Luis
