Commit faaae2a5 by Linus Torvalds

Re-enable CONFIG_MODVERSIONS in a slightly weaker form

This enables CONFIG_MODVERSIONS again, but allows for missing symbol CRC information in order to work around the issue that newer binutils versions seem to occasionally drop the CRC on the floor. binutils 2.26 seems to work fine, while binutils 2.27 seems to break MODVERSIONS of symbols that have been defined in assembler files. [ We've had random missing CRC's before - it may be an old problem that just is now reliably triggered with the weak asm symbols and a new version of binutils ] Some day I really do want to remove MODVERSIONS entirely. Sadly, today does not appear to be that day: Debian people apparently do want the option to enable MODVERSIONS to make it easier to have external modules across kernel versions, and this seems to be a fairly minimal fix for the annoying problem. Cc: Ben Hutchings <> Acked-by: 's avatarMichal Marek <> Signed-off-by: 's avatarLinus Torvalds <>
parent 22d3d4fb
......@@ -1945,7 +1945,6 @@ config MODULE_FORCE_UNLOAD
bool "Module versioning support"
depends on BROKEN
Usually, you have to use modules compiled with your kernel.
Saying Y here makes it sometimes possible to use modules
......@@ -1301,8 +1301,9 @@ static int check_version(Elf_Shdr *sechdrs,
goto bad_version;
pr_warn("%s: no symbol version for %s\n", mod->name, symname);
return 0;
/* Broken toolchain. Warn once, then let it go.. */
pr_warn_once("%s: no symbol version for %s\n", mod->name, symname);
return 1;
pr_warn("%s: disagrees about version of symbol %s\n",
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment