linux-kernel - side-effect when enabling CONFIG

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 18 Jul 2016 12:44:45 +0200
From:	Arend Van Spriel <arend.vanspriel@...adcom.com>
To:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: side-effect when enabling CONFIG_MODULES

A question for whoever can provide the answer. I have a kernel defconfig
with everything built-in. However, I want to compile a driver module
against it for testing. So I enabled CONFING_MODULES, but as a
side-effect several implicitly selected config options changed from
CONFIG_FOO=y to CONFIG_FOO=m giving me slightly different kernel at
least when looking at the vmlinux. So I just did sed -i 's/=m/=y/'
.config, but I was wondering if that step can be avoided somehow?

Regards,
Arend