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-prev] [day] [month] [year] [list]
Date:	Mon, 18 Jul 2016 13:51:07 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	Arend Van Spriel <arend.vanspriel@...adcom.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: side-effect when enabling CONFIG_MODULES

On Monday, July 18, 2016 12:44:45 PM CEST Arend Van Spriel wrote:
> 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?

It sounds like the options that are left out in the defconfig file
default to =m, which becomes =y if CONFIG_MODULES is not set.

make my_defconfig
echo "CONFIG_MODULES=y" >> .config
make oldconfig
make savedefconfig
cp defconfig arch/*/config/my_defconfig

	Arnd

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ