Date: Wed, 25 Nov 2015 11:06:41 -0800 From: "H. Peter Anvin" <hpa@...or.com> To: Kees Cook <keescook@...omium.org> CC: Mathias Krause <minipli@...glemail.com>, "kernel-hardening@...ts.openwall.com" <kernel-hardening@...ts.openwall.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Andy Lutomirski <luto@...capital.net>, Ingo Molnar <mingo@...hat.com>, Thomas Gleixner <tglx@...utronix.de>, x86-ml <x86@...nel.org>, Arnd Bergmann <arnd@...db.de>, Michael Ellerman <mpe@...erman.id.au>, linux-arch <linux-arch@...r.kernel.org>, PaX Team <pageexec@...email.hu>, Emese Revfy <re.emese@...il.com> Subject: Re: [PATCH 0/2] introduce post-init read-only memory On 11/25/2015 10:54 AM, Kees Cook wrote: >> >> We should not wait for compile-time support, that doesn't make any >> sense. What would be useful would be a way to override this on the >> command line -- that way, if disabling RO or RO-after-init memory makes >> something work, we have an instant diagnosis. > > Seems easiest to have an arg just skip calling mark_rodata_ro(). I can add that. > Exactly. -hpa
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.