linux-kernel - Re: vmlinux.lds: consolidate initcall sections

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]

Date:	Fri, 27 Oct 2006 13:44:13 -0600
From:	Matthew Wilcox <matthew@....cx>
To:	Andrew Morton <akpm@...l.org>
Cc:	Pavel Machek <pavel@....cz>, Greg KH <greg@...ah.com>,
	Stephen Hemminger <shemminger@...l.org>,
	Adrian Bunk <bunk@...sta.de>,
	Linus Torvalds <torvalds@...l.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-pci@...ey.karlin.mff.cuni.cz
Subject: Re: vmlinux.lds: consolidate initcall sections

On Fri, Oct 27, 2006 at 11:41:44AM -0700, Andrew Morton wrote:
> Add a vmlinux.lds.h helper macro for defining the eight-level initcall table,
> teach all the architectures to use it.

> @@ -48,13 +48,7 @@ SECTIONS
>    . = ALIGN(8);
>    __initcall_start = .;
>    .initcall.init : {
> -	*(.initcall1.init) 
> -	*(.initcall2.init) 
> -	*(.initcall3.init) 
> -	*(.initcall4.init) 
> -	*(.initcall5.init) 
> -	*(.initcall6.init) 
> -	*(.initcall7.init)
> +	INITCALLS
>    }
>    __initcall_end = .;

Why not make the INITCALLS macro include more:

+#define INITCALLS						\
+	__initcall_start = .;					\
+	.initcall.init : {					\
+		*(.initcall1.init)				\
+		*(.initcall2.init)				\
+		*(.initcall3.init)				\
+		*(.initcall4.init)				\
+		*(.initcall5.init)				\
+		*(.initcall6.init)				\
+		*(.initcall7.init)				\
+	}							\
+	__initcall_end = .;

Also, you might want to check the spaces at the front of your INITCALLS
macro; I see two spaces before the first tab.
-
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/