linux-kernel - how to handle indirect kconfig dependencies

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]

Message-Id: <20061116200741.fb607fe4.randy.dunlap@oracle.com>
Date:	Thu, 16 Nov 2006 20:07:41 -0800
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	lkml <linux-kernel@...r.kernel.org>
Cc:	zippel@...ux-m68k.org, jejb <james.bottomley@...eleye.com>
Subject: how to handle indirect kconfig dependencies

Hi,

I have a (randconfig) build of 2.6.19-rc5-mm2 with:

CONFIG_DEBUG_READAHEAD=y

which selects DEBUG_FS, so DEBUG_FS=y, but DEBUG_FS depends on
SYSFS, and SYSFS is not set in the randconfig.

This randconfig causes this build error:

fs/built-in.o: In function `debugfs_init':
inode.c:(.init.text+0xdb2): undefined reference to `kernel_subsys'

so the question is:
(How) can kconfig follow the dependency chain and either
- prevent this odd config combination or
- see that 'select DEBUG_FS' implies 'select SYSFS' and then enable SYSFS
?

I don't believe that the right answer is to add
	depends on SYSFS
to DEBUG_READAHEAD.


.config is at http://oss.oracle.com/~rdunlap/configs/config-readahead-debugfs

Thanks,
---
~Randy [or just kill off select]
-
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/