| 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
| ||
|
Date: Wed, 30 Oct 2013 04:07:44 +0100 From: Michael Opdenacker <michael.opdenacker@...e-electrons.com> To: Michal Marek <mmarek@...e.cz> CC: Joe Perches <joe@...ches.com>, yann.morin.1998@...e.fr, akpm@...ux-foundation.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] scripts/checkkconfig.py: find unused Kconfig parameters Hi Michal, Thank you very much for your reviews! On 10/25/2013 03:45 PM, Michal Marek wrote: > You can process Kconfig files and source files separately. And you can > speed up the script a lot, if you simply record all CONFIG_* strings > found in the sources, and then compare this to the set of config options > defined in Kconfig. Then you can also easily implement the opposite > check, which is currently done by scripts/checkkconfigsymbols.sh. I like the idea. CONFIG_* strings at least should be easy to identify in the source code indeed. I'll also have to find all the parameters referred to in Kconfig files (namely as dependencies), but this should be worth the effort. The whole program will be a bit more complex, but it will be orders of magnitude faster! Thanks again, Michael. -- Michael Opdenacker, CEO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com +33 484 258 098 -- 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