Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755200AbbK0SDE (ORCPT ); Fri, 27 Nov 2015 13:03:04 -0500 Received: from mail-io0-f178.google.com ([209.85.223.178]:34791 "EHLO mail-io0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755013AbbK0SDC (ORCPT ); Fri, 27 Nov 2015 13:03:02 -0500 MIME-Version: 1.0 In-Reply-To: References: <1448401114-24650-1-git-send-email-keescook@chromium.org> <565595F5.32536.DB9FE75@pageexec.freemail.hu> <20151126085425.GA29848@gmail.com> <20151127075959.GA24991@gmail.com> Date: Fri, 27 Nov 2015 10:03:01 -0800 X-Google-Sender-Auth: YcYUUi2dqkFmZeb0MhpHzxcRhX8 Message-ID: Subject: Re: [kernel-hardening] [PATCH 0/2] introduce post-init read-only memory From: Linus Torvalds To: Ingo Molnar Cc: Andy Lutomirski , PaX Team , "kernel-hardening@lists.openwall.com" , Mathias Krause , "linux-kernel@vger.kernel.org" , Kees Cook , Ingo Molnar , Thomas Gleixner , "H. Peter Anvin" , x86-ml , Arnd Bergmann , Michael Ellerman , linux-arch , Emese Revfy Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 922 Lines: 22 On Fri, Nov 27, 2015 at 10:00 AM, Linus Torvalds 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/