linux-kernel - Re: [PATCH] also discard .*init sections after module initialization

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 07 Jul 2009 07:27:04 +0100
From:	"Jan Beulich" <JBeulich@...ell.com>
To:	"Tim Abbott" <tabbott@...lice.com>, <tabbott@....EDU>
Cc:	<tony.luck@...el.com>,
	"Benjamin Herrenschmidt" <benh@...nel.crashing.org>,
	<sam@...nborg.org>, "Rusty Russell" <rusty@...tcorp.com.au>,
	"Paul Mackerras" <paulus@...ba.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] also discard .*init sections after
	 module	initialization

>>> Tim Abbott <tabbott@...lice.com> 06.07.09 17:55 >>>
>On Wed, 1 Jul 2009, Jan Beulich wrote:
>> Why? .*exit sections deal with device/memory/CPU hot remove, which is
>> orthogonal to module unload.
>
>For the core kernel, the .devinit sections are currently being squashed 
>into either the .data section or the .init.data section depending on 
>whether hotplug is enabled using the vmlinux linker scripts.  Can we use 
>the same approach for modules (i.e. have a module linker script that does 
>this)?  It seems that would avoid having two duplicate mechanisms for 
>doing the same thing, one in the module loader and one in the core 
>kernel's linker scripts.

I'd have to play with this a little, as I'm not sure ld -r can actually do what
you're suggesting.

Jan

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