kernel-hardening - Re: [PATCH 0/2] introduce post-init read-only memory

Follow @Openwall on Twitter for new release announcements and other news

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

Message-ID: <20151129080853.GB23721@gmail.com>
Date: Sun, 29 Nov 2015 09:08:53 +0100
From: Ingo Molnar <mingo@...nel.org>
To: PaX Team <pageexec@...email.hu>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
	kernel-hardening@...ts.openwall.com,
	Mathias Krause <minipli@...glemail.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Kees Cook <keescook@...omium.org>,
	Andy Lutomirski <luto@...capital.net>,
	Ingo Molnar <mingo@...hat.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>, x86-ml <x86@...nel.org>,
	Arnd Bergmann <arnd@...db.de>,
	Michael Ellerman <mpe@...erman.id.au>, linux-arch@...r.kernel.org,
	Emese Revfy <re.emese@...il.com>
Subject: Re: [PATCH 0/2] introduce post-init read-only
 memory


* PaX Team <pageexec@...email.hu> 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

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