| 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: Thu, 15 Oct 2009 08:45:59 -0700 From: Daniel Walker <dwalker@...o99.com> To: Gregory Haskins <gregory.haskins@...il.com> Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: Tips for module_init() dependencies On Thu, 2009-10-15 at 09:01 -0400, Gregory Haskins wrote: > may break, because the kernel seems to have no concept of > interdependency between foo_init() and bar_init(), and therefore > bar_init() may call foo() before foo_init() has executed. > > There are various ways to solve this problem, such as deferring calling > foo() with a workqueue or something, but I was wondering if there was a > better/standard way to do this that I am missing? > > The problem I am having specifically is that I am trying to call > configfs_register_subsystem() in a module_init(), but this breaks when > built into the kernel based on sheer bad luck that configfs gets > initialized after me. To date I have worked around this by forcing my > code to only support built-in, and using late_initcall() instead or > module_init. This works, but it only means I am putting the problem off > (code that depends on *me* has to use similar tricks, etc. You can't modify the build order so your module get "builtin" after configfs? 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/
Powered by blists - more mailing lists