It's not the module versioning that will break it. Without module versioning,
it'll still be broken if you load modules which don't match the kernel.
I suspect that the real fix is in fact to rethink the module versioning. There
are a number of cases where compatible modules have different version numbers,
and incompatible ones have the same version numbers.
However, I prefer to follow up my suggestions with at least a snippet of code,
and have no clue how the version system works ATM, (or doesn't work, as the
case may be).
----------
Note that there are two problems addressed by module versioning:
- It makes it possible to load modules from one kernel into another version,
if they are compatible.
- It also catches the cases where modules compiled from the same source, but
with different config options, are incompatible, and stops you loading
the offending modules.
The first we require to support binary-only modules sensibly.
The second is the one I'm more interested in, and to which I'm referring.
---- ---- ----
David Woodhouse, Robinson College, CB3 9AN, England. (+44) 0976 658355
Dave@imladris.demon.co.uk http://dwmw2.robinson.cam.ac.uk
finger pgp@dwmw2.robinson.cam.ac.uk for PGP key.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu