From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755210AbdC1TDL (ORCPT ); Tue, 28 Mar 2017 15:03:11 -0400 Received: from mail-it0-f54.google.com ([209.85.214.54]:33132 "EHLO mail-it0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751921AbdC1TDJ (ORCPT ); Tue, 28 Mar 2017 15:03:09 -0400 MIME-Version: 1.0 In-Reply-To: References: <1485894263-91051-1-git-send-email-keescook@chromium.org> <1485894263-91051-2-git-send-email-keescook@chromium.org> <851a0c99-db08-c3a8-f5c6-2e567971e2eb@au1.ibm.com> From: Kees Cook Date: Tue, 28 Mar 2017 12:03:07 -0700 X-Google-Sender-Auth: Oaawq5YjCQLHLKkeoxTH3F_XaZI Message-ID: Subject: Re: [kernel-hardening] [PATCH v5 1/4] gcc-plugins: Add the initify gcc plugin To: Arnd Bergmann Cc: Andrew Donnellan , LKML , Emese Revfy , Josh Triplett , PaX Team , Masahiro Yamada , minipli@ld-linux.so, Russell King , Catalin Marinas , Rasmus Villemoes , David Brown , "benh@kernel.crashing.org" , Thomas Gleixner , Andrew Morton , Jeff Layton , Sam Ravnborg , "kernel-hardening@lists.openwall.com" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Mar 28, 2017 at 12:49 AM, Arnd Bergmann wrote: > On Mon, Mar 27, 2017 at 6:14 PM, 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. > > I've tried turning it on again a few days ago and still got too many build > problems with my randconfig tree, so I've turned it off again. I think I've > already reported most of what I found now, so I did not send out new > reports. Hrm, with what's in -next? That's too bad. I thought everything you reported had been fixed. Dang. :( -Kees -- Kees Cook Pixel Security From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 Sender: keescook@google.com In-Reply-To: References: <1485894263-91051-1-git-send-email-keescook@chromium.org> <1485894263-91051-2-git-send-email-keescook@chromium.org> <851a0c99-db08-c3a8-f5c6-2e567971e2eb@au1.ibm.com> From: Kees Cook Date: Tue, 28 Mar 2017 12:03:07 -0700 Message-ID: Content-Type: text/plain; charset=UTF-8 Subject: Re: [kernel-hardening] [PATCH v5 1/4] gcc-plugins: Add the initify gcc plugin To: Arnd Bergmann Cc: Andrew Donnellan , LKML , Emese Revfy , Josh Triplett , PaX Team , Masahiro Yamada , minipli@ld-linux.so, Russell King , Catalin Marinas , Rasmus Villemoes , David Brown , "benh@kernel.crashing.org" , Thomas Gleixner , Andrew Morton , Jeff Layton , Sam Ravnborg , "kernel-hardening@lists.openwall.com" List-ID: On Tue, Mar 28, 2017 at 12:49 AM, Arnd Bergmann wrote: > On Mon, Mar 27, 2017 at 6:14 PM, 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. > > I've tried turning it on again a few days ago and still got too many build > problems with my randconfig tree, so I've turned it off again. I think I've > already reported most of what I found now, so I did not send out new > reports. Hrm, with what's in -next? That's too bad. I thought everything you reported had been fixed. Dang. :( -Kees -- Kees Cook Pixel Security