Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 27 Mar 2017 21:31:02 +0200
From: Rasmus Villemoes <>
To: Kees Cook <>
Cc: Andrew Donnellan <>,  LKML <>,  Emese Revfy <>,  Arnd Bergmann <>,  Josh Triplett <>,  PaX Team <>,  Masahiro Yamada <>,,  Russell King <>,  Catalin Marinas <>,  David Brown <>,  "benh\" <>,  Thomas Gleixner <>,  Andrew Morton <>,  Jeff Layton <>,  Sam Ravnborg <>,  "kernel-hardening\" <>
Subject: Re: [PATCH v5 1/4] gcc-plugins: Add the initify gcc plugin

On Mon, Mar 27 2017, Kees Cook <> wrote:

> On Mon, Mar 27, 2017 at 12:38 AM, Andrew Donnellan
> <> wrote:
>> On 01/02/17 07:24, Kees Cook wrote:
>>> From: Emese Revfy <>
>>> 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.
>> Currently checking whether we can wire this up for powerpc without too many
>> problems...
> Cool, thanks. FWIW, note that this plugin is a bit back-burnered at
> the moment. I've got this in my -next tree still, but it needs some
> rather large changes to how it does its annotations before Linus will
> accept it.

Why not just hardcode the annotations in the plugin itself? I'd expect
just making it know about mem*, str*, and the various *printf/printk
functions would get 90% of the benefits. The prototypes of these 
aren't gonna change anytime soon, so there's no compelling reason to
keep the annotations with the declarations. The plugin can still do
its sanity checking when it compiles a function with one of these names.


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.