A runtime check is still done, with per-module vermagic which distrosOn the other hand the big advantage of modversions is that it alsoThe question is how to provide a similar guarantee if a different way?As a tool to aid distro reviewers, modversions has some value, but the
debug info parsing tools that have been mentioned in this thread seem
superior (not that I've tested them).
verifies the checksum during runtime (module loading). In other words, I
believe that any other solution should still generate some form of
checksum/watermark which can be easily checked for compatibility on
It should not be hard to add to the DWARF based tools though. We'd just
parse DWARF data instead of the C code.
can change when they bump the ABI version. Is it really necessary to
have more than that (i.e., per-symbol versioning)?