linux-kernel - x86: defconfig not being applied automatically in 2.6.24+

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>] [day] [month] [year] [list]

Message-ID: <47F542BE.3000106@gentoo.org>
Date:	Thu, 03 Apr 2008 21:49:02 +0100
From:	Daniel Drake <dsd@...too.org>
To:	Sam Ravnborg <sam@...nborg.org>
CC:	linux kernel <linux-kernel@...r.kernel.org>, kerframil@...il.com,
	mpagano@...too.org, linux-kbuild@...r.kernel.org
Subject: x86: defconfig not being applied automatically in 2.6.24+

In 2.6.23, if you unpacked a kernel source tarball and then ran "make 
menuconfig" you'd be presented with this message:
	# using defaults found in arch/i386/defconfig

and the default options would be set.

The same thing in 2.6.24 does not give you any "using defaults" message, 
and the default config options within menuconfig are rather blank (e.g. 
no PCI support). You can work around this by explicitly running "make 
defconfig" before menuconfig, but it would be nice to have the behaviour 
the way it was for 2.6.23 (and the way it still is for other archs).

I've looked into the problem. It works on 2.6.23 because of init/Kconfig 
which is still unchanged:

config DEFCONFIG_LIST
	[...]
	default "arch/$ARCH/defconfig"

arch/i386/defconfig and arch/x86_64/defconfig existed in 2.6.23, but not 
in 2.6.24 due to the arch merge.

I've identified why it worked in 2.6.23 but I'm not really sure of the 
right way to fix it for the newer kernels. I tried adding another 
default in DEFCONFIG_LIST:
	default "arch/$SRCARCH/configs/$KBUILD_DEFCONFIG"
but it seems that $SRCARCH and $KBUILD_DEFCONFIG are not being exported 
to kconfig and I couldn't immediately see how to change that.

Any thoughts?

Thanks,
Daniel
--
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/