linux-kernel - Re: [PATCH 13/15] kmemleak: Keep the __init functions after 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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Wed, 10 Dec 2008 19:44:10 +0100
From:	Sam Ravnborg <sam@...nborg.org>
To:	Catalin Marinas <catalin.marinas@....com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 13/15] kmemleak: Keep the __init functions after initialization

On Wed, Dec 10, 2008 at 06:28:06PM +0000, Catalin Marinas wrote:
> This patch adds the CONFIG_DEBUG_KEEP_INIT option which preserves the
> .init.* sections after initialization. Memory leaks happening during
> this phase can be more easily tracked.

This patch manipulate the section names of these functions.
The better way would be to keep the section names as they are
and then in init.h decide where to add these sections.

This will require a new set of CONFIG_ symbols but then
it is obvious what happens.

Something like:

config	KEEP_INIT
	bool

config	KMEMLEAK
	...
	select KEEP_INIT
	select DEBUG_KEEP_CPUINIT
	select DEBUG_KEEP_MEMINIT

config HOTPLUG
	...
	select KEEP_INIT

And then use these symbols in vmlinux.lds.h

	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/