linux-kernel - Re: [PATCH] arch/cris/arch-v10/vmlinux.lds.S fix boot problem

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: <20071222083717.GB22653@uranus.ravnborg.org>
Date:	Sat, 22 Dec 2007 09:37:17 +0100
From:	Sam Ravnborg <sam@...nborg.org>
To:	Jesper Nilsson <jesper.nilsson@...s.com>
Cc:	Yuusei KUWANA <kuwana@...nyan.to>,
	Linux Kernel list <linux-kernel@...r.kernel.org>,
	mikael.starvik@...s.com
Subject: Re: [PATCH] arch/cris/arch-v10/vmlinux.lds.S fix boot problem

Hi Jesper.

>  		__initramfs_end = .;
> -		/* We fill to the next page, so we can discard all init
> -		   pages without needing to consider what payload might be
> -		   appended to the kernel image.  */
> -		FILL (0); 
> -		. = ALIGN (8192);
>  	}
>  #endif
> -	
>  	__vmlinux_end = .;            /* last address of the physical file */
> -  	__init_end = .;
> +
> +	/*
> +	 * We fill to the next page, so we can discard all init
> +	 * pages without needing to consider what payload might be
> +	 * appended to the kernel image.
> +	 */
> +	.init.fill : {
> +		FILL (0);
> +		. = ALIGN (8192);
> +	}
> +
> +	__init_end = .;

Can we please have the hardcoded 8192 replaced with a proper constant.
I assume this is PAGESIZE?
See hwat other archs does to make PAGESIZE available for assembly
files and ldscripts. The macro AC is the key point here.

And then please explain why it make a diffrence to put the
alignment in a section like you do.
I do not see it used in the other archs.

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