Re: [PATCH] Early init for security modules

[Chris Wright]

* Chris Wright ([e-mail]) wrote:
> As discussed before, here is a simple patch to allow for early
> initialization of security modules when compiled statically into the
> kernel.  The standard do_initcalls is too late for complete coverage of
> all filesystems and threads for example.  If this looks OK, I'd like to
> push it on to Linus.  Patch is against 2.5.69-bk.  It is tested on i386,
> and various arch maintainers are copied on relevant bits of patch.

This is just the arch specific linker bits for the early initialization
for security modules patch.  Does this look sane for this arch?

--- 1.16/arch/m68k/vmlinux-std.lds	Wed Apr  2 00:42:56 2003
+++ edited/arch/m68k/vmlinux-std.lds	Mon May 12 16:16:58 2003
@@ -67,6 +67,9 @@
   __con_initcall_start = .;
   .con_initcall.init : { *(.con_initcall.init) }
   __con_initcall_end = .;
+  __security_initcall_start = .;
+  .security_initcall.init : { *(.security_initcall.init) }
+  __security_initcall_end = .;
   . = ALIGN(8192);
   __initramfs_start = .;
   .init.ramfs : { *(.init.ramfs) }

--- 1.14/arch/m68k/vmlinux-sun3.lds	Wed Apr  2 00:42:56 2003
+++ edited/arch/m68k/vmlinux-sun3.lds	Mon May 12 16:16:59 2003
@@ -61,6 +61,9 @@
 	__con_initcall_start = .;
 	.con_initcall.init : { *(.con_initcall.init) }
 	__con_initcall_end = .;
+	__security_initcall_start = .;
+	.security_initcall.init : { *(.security_initcall.init) }
+	__security_initcall_end = .;
 	. = ALIGN(8192);
 	__initramfs_start = .;
 	.init.ramfs : { *(.init.ramfs) }