Bug 14411 - [FR] automatic kernel module check for symbol-related problems
: [FR] automatic kernel module check for symbol-related problems
Status: ASSIGNED
: Sisyphus
(All bugs in Sisyphus/rpm-build-kernel)
: unstable
: all Linux
: P2 enhancement
Assigned To:
:
:
:
:
: 14408
  Show dependency tree
 
Reported: 2008-02-13 11:18 by
Modified: 2009-09-13 17:08 (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2008-02-13 11:18:36
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 .
------- Comment #1 From 2008-02-13 13:30:51 -------
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.
------- Comment #2 From 2008-02-13 13:57:23 -------
(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.
------- Comment #3 From 2009-09-13 17:08:19 -------
Guess VM support is out of rpm-build-kernel scope.