linux-kernel - Re: [PATCH] x86: fix improper .init-type section references

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

Date:	Wed, 13 Jun 2007 10:10:49 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Satyam Sharma <satyam.sharma@...il.com>
Cc:	Jan Beulich <jbeulich@...ell.com>,
	Venkatesh Pallipadi <venkatesh.pallipadi@...el.com>,
	Andi Kleen <ak@...e.de>, linux-kernel@...r.kernel.org,
	patches@...-64.org
Subject: Re: [PATCH] x86: fix improper .init-type section references

On Wed, Jun 13, 2007 at 01:09:07PM +0530, Satyam Sharma wrote:
> 
> i.e. don't discard anything at build time, and link the .exit.{text,
> data} sections
> into the kernel image for _all_ archs? (otherwise how do we avoid
> special-casing/
> checking for the arch in modpost and warn/not-warn about invalid/valid 
> cases)
> 
> But then why not simply lose the __exit (and .exit.*) altogether? Because
> __exit becomes redundant in the suggested changed semantics -- just mark
> all the cleanup code as __init too (when it's built-in, the only
> callsite for the
> cleanup code would be from the startup code in .init.*, and when modular,
> __init and __exit lose all relevance anyway).

The reason we do it today is to save memory in a memory constrained environment.
So with such a suggestion you should back it up with numbers.

How much RAM is wasted by keeping the __init and _exit sections
in memory for a normal embedded build?

You could try a random defconfig for arm or mips since they are
embedded in general. Using defconfig for i386 could tell us
a little but not that important.

And when evaluating the numbers think of maybe 8 MB RAM in total, no swap
storage, and sloow filesystem for permanent storage.

	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/