From mboxrd@z Thu Jan 1 00:00:00 1970 Reply-To: kernel-hardening@lists.openwall.com Sender: Ingo Molnar Date: Sun, 29 Nov 2015 09:08:53 +0100 From: Ingo Molnar Message-ID: <20151129080853.GB23721@gmail.com> References: <1448401114-24650-1-git-send-email-keescook@chromium.org> <5656F7A2.738.131F89C0@pageexec.freemail.hu> <20151127080554.GB24991@gmail.com> <565876F3.21515.18F8DF8F@pageexec.freemail.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <565876F3.21515.18F8DF8F@pageexec.freemail.hu> Subject: Re: [kernel-hardening] [PATCH 0/2] introduce post-init read-only memory To: PaX Team Cc: Linus Torvalds , kernel-hardening@lists.openwall.com, Mathias Krause , "linux-kernel@vger.kernel.org" , Kees Cook , Andy Lutomirski , Ingo Molnar , Thomas Gleixner , "H. Peter Anvin" , x86-ml , Arnd Bergmann , Michael Ellerman , linux-arch@vger.kernel.org, Emese Revfy List-ID: * PaX Team wrote: > i don't see the compile time vs. runtime detection as 'competing' approaches, > both have their own role. [...] That's true - but only as long as 'this can be solved in tooling!' is not used as an excuse to oppose the runtime solution and we end up doing neither. Thanks, Ingo