Messages in this thread | | | Date | Sat, 20 Dec 1997 23:51:40 +0100 | From | Martin von Loewis <> | Subject | Re: Module versioning (was: Re: OFFTOPIC: binary modules, bad idea!) |
| |
> The major problem with module versionning is not that much related to the > technology (ELF trickery or preprocessor solution with .ver file). The > problem is that genksyms does not know where to stop. This is a kernel > header issue. Let me explain with an example.
Is *this* the real issue? I would imagine that the scenario presented rarely happens; i.e. if you change a structure, you do break the modules that call functions expecting pointers to these structures.
It would be interesting to analyze what symbol versions changed during the life of Linux 2.0, and what modules are affected by those.
If there are some functions that frequently break even though the parameters are meant to be opaque, then the parameters should be changed to actually be opaque (say, void* or the like).
Regards, Martin
| |