| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <Y165ES5i.1222268879.9618400.pluto@agmk.net> Date: Wed, 24 Sep 2008 17:07:59 +0200 From: "Paweł Sikora" <pluto@...k.net> To: linux-kernel@...r.kernel.org Subject: [kernel-abi] symbol versioning vs. out-of-tree modules. Hi All, with out-of-tree kernel modules we (users and linux distributions) have a problem - with every frequent kernel release we need to rebuild them all due to vermagic and possible abi changes. this leads to lot of useless work (bumping rpm specs releases, preparing rpm packages and so on). naturally we could workaround the modprobe vermagic errors but we currently can't detect the big-bang kernel abi changes. e.g., some kernel function changes its parameter list while the exported function(symbol) name still staying unchanged. finally we get a modprobe-big-bang. in fact, we can't use a c++ symbol name mangling to avoid such problems but kernel build system could use a linker script to versioning symbols (like glibc/libgcc). during the abi change, kernel developers could just bump the symbol version and external modules could be refused during loading with 'unresolved symbol' error which is imho much better solution that an oops. is it acceptable and possible to introducing such solution? thanks for comments. BR, pawel. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists