when adding a kernel module weak-module does not collect the symbols from external modules of destination kernel

Solution In Progress - Updated -

Issue

When adding a module that has a different version to a kernel, weak-modules looks into the symbols of the destination kernel, but does not looks into the external modules already installed for that kernel. If some symbol is defined by one of these external modules, weak module returns that the new module "is not compatible"

Steps:
1. build some external modules m1 and m2 on kernel version n. module m2 imports some symbols from m1.
2. install kernel n and modules m1 and m2 (that install in /lib/modules/n/extra for example)
3. build module m2 on kernel version n+1 (with same kabi).
install module m2 will fail

The result is that no link created in /lib/modules/n+1/weak-modules, while one would expect a link to be created

Environment

  • Red Hat Entreprise Linux (RHEL) 6

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content