Date: Fri, 27 Nov 2015 10:03:01 -0800 From: Linus Torvalds <torvalds@...ux-foundation.org> To: Ingo Molnar <mingo@...nel.org> Cc: Andy Lutomirski <luto@...capital.net>, PaX Team <pageexec@...email.hu>, "kernel-hardening@...ts.openwall.com" <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>, 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 <linux-arch@...r.kernel.org>, Emese Revfy <re.emese@...il.com> Subject: Re: [PATCH 0/2] introduce post-init read-only memory On Fri, Nov 27, 2015 at 10:00 AM, Linus Torvalds <torvalds@...ux-foundation.org> wrote: > > - just oops and kill the machine, like for any other unhandled kernel > page fault. This is probably what you should have on a server Just to clarify: the "just oops" obviously doesn't have to kill the machine, it depends on what your oops policy is, with the default obviously being the normal "kill that particular thread" if at all possible. Machine-killing is appropriate in some secure situations, but most of the time it just makes it too damn hard to debug since the error often doesn't get logged. In some situations we obviously can't avoid it, but.. Linus
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.