14411 2008-02-13 11:18:36 +0300 [FR] automatic kernel module check for symbol-related problems 2009-09-13 17:08:19 +0400 1 1 4 Development Sisyphus rpm-build-kernel unstable all Linux ASSIGNED P2 enhancement --- 14408 1 imz vsu boyarsh glebfm kernelbot ldv mike rider sbolshakov shrek sin vitty vsu vt zerg qa-sisyphus oldest_to_newest 63080 0 imz 2008-02-13 11:18:36 +0300 rpm-build-kernel-0.11-alt1 After modules have been compiled, it would be nice to check if they can be loaded into the corresponding kernel, whether they have no unknown symbols. Before it happens in a working system. Perhaps, module-init-tools are able to do such a check (not for the running kernel), or it could be done in a hardware emulator. This feature request was inspired by https://bugzilla.altlinux.org/show_bug.cgi?id=14408 , https://bugzilla.altlinux.org/show_bug.cgi?id=14409 . 63086 1 vsu 2008-02-13 13:30:51 +0300 The kernel build system already does some checks for undefined symbols; unfortunately, even in 2.6.24 failures of these checks when building external modules are just warnings. However, the real problem with drm is not undefined symbols, but multiple definitions of symbols (the drm module cannot be loaded due to the duplicate idr_remove_all definition, and then all modules which depend on it fail with unresolved symbols), and the uhci_hcd problem is due to races between concurrent modprobe invocations. 63092 2 imz 2008-02-13 13:57:23 +0300 (In reply to comment #1) > However, the real problem with drm is not undefined symbols, but multiple > definitions of symbols (the drm module cannot be loaded due to the duplicate > idr_remove_all definition, I see. Added "multiple definitions of symbols" to the summary. 99004 3 mike 2009-09-13 17:08:19 +0400 Guess VM support is out of rpm-build-kernel scope.