linux-kernel - Re: [PATCH v3 6/7] m68knommu: Move __init

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: <alpine.DEB.1.10.0910142041520.6638@dr-wily.mit.edu>
Date:	Sun, 18 Oct 2009 13:22:33 -0400 (EDT)
From:	Tim Abbott <tabbott@...lice.com>
To:	Sam Ravnborg <sam@...nborg.org>
cc:	Greg Ungerer <gerg@...pgear.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 6/7] m68knommu: Move __init_end out of the .init
 section.

On Wed, 14 Oct 2009, Sam Ravnborg wrote:

> Took a look at this trying to understand why this
> caused a non-booting system.

Thanks, I really appreciate your looking at this!

[...]
> I think the better solution is to use the same section name
> several times like this:
> 
> 	.init : {
>               . = ALIGN(PAGE_SIZE);
>               __init_end = .;
>       } > INIT
> 
> We should do this both for begin and end.
> Then the linker will not fool us and try to rearrange stuff.
> And we do not end up with zero sized sections.

OK, I have an attempt at implementing this idea.  Of course, the final 
patch which uses INIT_TEXT_SECTION and INIT_DATA_SECTION has multiple 
output sections (.init.data and .init.text), but I think perhaps including 
these alignment guards in the adjacent section might work.

	-Tim Abbott

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