Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 29 Jun 2016 07:50:25 -0700
From: Kees Cook <>
To: Rasmus Villemoes <>
Cc: Emese Revfy <>, 
	"" <>, PaX Team <>, 
	Brad Spengler <>, Michal Marek <>, 
	LKML <>, 
	Masahiro Yamada <>, linux-kbuild <>,, Russell King <>, 
	Catalin Marinas <>, David Brown <>, 
	"" <>, Thomas Gleixner <>, 
	Andrew Morton <>,, 
	Arnd Bergmann <>
Subject: Re: [PATCH v1 1/2] Add the initify gcc plugin

On Tue, Jun 28, 2016 at 2:05 PM, Rasmus Villemoes
<> wrote:
> On Tue, Jun 28 2016, Emese Revfy <> wrote:
>> The kernel already has a mechanism to free up code and data memory that
>> is only used during kernel or module initialization.
>> This plugin will teach the compiler to find more such code and data that
>> can be freed after initialization.
>> It has two passes. The first one tries to find all functions that
>> can be become __init/__exit. The second one moves string constants
>> (local variables and function string arguments marked by
>> the nocapture attribute) only referenced in __init/__exit functions
>> to the __initconst/__exitconst sections.
>> It reduces memory usage. This plugin can be useful for embedded systems.
> May I suggest, as a followup patch, a debug option/plugin parameter to
> put the strings in a section which will not be reaped after init, but
> just marked inaccessible, with graceful handling of bad accesses (print
> a big fat warning, make the page(s) readable, continue)?

Is there a clean way to do this that isn't arch-specific?


Kees Cook
Chrome OS & Brillo Security

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.