| 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: Fri, 07 May 2010 12:31:19 +0100 From: Catalin Marinas <catalin.marinas@....com> To: James Bottomley <James.Bottomley@...senPartnership.com> Cc: linux-arch@...r.kernel.org, linux-kernel <linux-kernel@...r.kernel.org>, Sam Ravnborg <sam@...nborg.org>, linux-kbuild@...r.kernel.org, Randy Dunlap <randy.dunlap@...cle.com> Subject: Re: kbuild: fixing the select problem James Bottomley <James.Bottomley@...senPartnership.com> wrote: > The select problem is that the kbuild select directive will turn a > symbol on without reference to its dependencies. This, in turn, means > that either selected symbols must select their dependencies, or that > people using select have to be aware of the selected symbol's dependency > and build those dependencies into their symbol (leading to duplication > and the possibility of getting the dependencies out of sync). We use > select for the scsi transport classes, so we run into this problem in > SCSI quite a lot. > > I think the correct fix is to make a symbol that selects another symbol > automatically inherit all of the selected symbol's dependencies. You may want to have a look at a patch I proposed some time ago, which at just warns of selecting options with unmet dependencies. I think it's a better approach that forcing the selection of the dependencies: http://lkml.org/lkml/2009/9/16/413 -- Catalin -- 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