| 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
| ||
|
Message-ID: <4AD74B02.1070606@gmail.com>
Date: Thu, 15 Oct 2009 12:17:06 -0400
From: Gregory Haskins <gregory.haskins@...il.com>
To: Daniel Walker <dwalker@...o99.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Tips for module_init() dependencies
Daniel Walker wrote:
> On Thu, 2009-10-15 at 11:58 -0400, Gregory Haskins wrote:
>
>> Hi Daniel,
>>
>> Possibly.
>>
>> A) Any suggestions on how? Can I express this in Kconfig or something
>> (i.e. "depends on FOO"). I currently have "select FOO" in the BAR
>> object, but this doesn't seem to be sufficient to describe the relationship.
>>
>> B) Do I have to make the entire chain follow suit? (I have C deps on B,
>> B deps on A kind of scenarios)
>
> Yeah, what Randy said .. As far as I know it should be just a build
> order issue .. In the make file when you specify your new module along
> with all the others where you put it is actually important .. In
> fs/Makefile you have this line,
>
> obj-$(CONFIG_CONFIGFS_FS) += configfs/
>
> and I would guess you want yours after that line if your adding to that
> makefile.
Right, that makes sense. However, the problem is that these
dependencies might not have anything to do with ./fs per se and
therefore would not necessarily be in the ./fs Makefile. But I think
the Makefile dependency idea in general is the right approach, so I will
experiment with this suggestion.
Kind Regards,
-Greg
Download attachment "signature.asc" of type "application/pgp-signature" (268 bytes)
Powered by blists - more mailing lists