linux-kernel - post_coreinitcall and module_init() in tty

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

Message-Id: <20071018101047.M27270@cdotd.ernet.in>
Date:	Thu, 18 Oct 2007 16:41:06 +0630
From:	"Deepak Gaur" <dgaur@...td.ernet.in>
To:	linux-kernel@...r.kernel.org
Subject: post_coreinitcall and module_init() in tty_io.c linux kernel 2.6.10

Hi all,

I am novice in field of linux device drivers. I have a small question regarding module
_init() call in file drivers/char/tty_io.c. In this file there are two init calls mentioned

(a) postcore_initcall(tty_class_init);
(b) module_init(tty_init);

The postcore_initcall is defined in include/linux/init.h as
-----------------------------------------------------------------------
/**
 * module_init() - driver initialization entry point
 * @x: function to be run at kernel boot time or module insertion
 *
 * module_init() will either be called during do_initcalls (if
 * builtin) or at module insertion time (if a module).  There can only
 * be one per module.
 */
#define module_init(x)  __initcall(x);

/**
 * module_exit() - driver exit entry point
 * @x: function to be run when driver is removed
 *
 * module_exit() will wrap the driver clean-up code
 * with cleanup_module() when used with rmmod when
 * the driver is a module.  If the driver is statically
 * compiled into the kernel, module_exit() has no effect.
 * There can only be one per module.
 */
#define module_exit(x)  __exitcall(x);

#else /* MODULE */

/* Don't use these in modules, but some people do... */
#define core_initcall(fn)               module_init(fn)
#define postcore_initcall(fn)           module_init(fn)
#define arch_initcall(fn)               module_init(fn)
#define subsys_initcall(fn)             module_init(fn)
#define fs_initcall(fn)                 module_init(fn)
#define device_initcall(fn)             module_init(fn)
#define late_initcall(fn)               module_init(fn)

---------------------------------------------------------

It's written in quoted text that "There can only be one per module". But in tty_io.c
there are two; postcore_initcall also maps to module_init. Each call is using different
init functions and both functions seems to be required to be executed for proper
functioning of module.

So my query is

(1) Which one of the two (postcore_initcall/module_init) get executed and when?
(2) If both get executed does it not break the rule that a kernel module should have
only one module_init() and one module_exit()?

with warm regards

Deepak Gaur
------- End of Forwarded Message -------

Deepak Gaur

-
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/