Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965242AbeALRzx (ORCPT + 1 other); Fri, 12 Jan 2018 12:55:53 -0500 Received: from mail-io0-f174.google.com ([209.85.223.174]:45498 "EHLO mail-io0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S964844AbeALRzr (ORCPT ); Fri, 12 Jan 2018 12:55:47 -0500 X-Google-Smtp-Source: ACJfBovpFcnDH4dpAe8I/lncz63mVGwVL+jrF/t5Tt1GIZgIzojw6hBcpLrXRJ86Ew5wjgwrmsMd7brtajBK2WT9PZs= MIME-Version: 1.0 In-Reply-To: <6590e2b183c740f6896f57ae100c2ac3@AcuMS.aculab.com> References: <1515502580-12261-1-git-send-email-w@1wt.eu> <1515502580-12261-7-git-send-email-w@1wt.eu> <20180110082207.GX29822@worktop.programming.kicks-ass.net> <20180110091102.GH14066@1wt.eu> <20180111064259.GC14920@1wt.eu> <0f08d89e-61e1-20e3-5c59-0b2f7b32bf0c@linux.intel.com> <20180111154412.GA15296@1wt.eu> <20180111174025.GB15344@1wt.eu> <6590e2b183c740f6896f57ae100c2ac3@AcuMS.aculab.com> From: Linus Torvalds Date: Fri, 12 Jan 2018 09:55:45 -0800 X-Google-Sender-Auth: JYDnVjmwBzg8uIetJ9VH7C-18s0 Message-ID: Subject: Re: [RFC PATCH v2 6/6] x86/entry/pti: don't switch PGD on when pti_disable is set To: David Laight Cc: Willy Tarreau , Andy Lutomirski , Dave Hansen , Peter Zijlstra , LKML , X86 ML , Borislav Petkov , Brian Gerst , Ingo Molnar , Thomas Gleixner , Josh Poimboeuf , "H. Peter Anvin" , Greg Kroah-Hartman , Kees Cook Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On Fri, Jan 12, 2018 at 8:27 AM, David Laight wrote: > > You need to allow for libraries that create threads before main() > is called. I really don't think we do. I think the normal case is the wrapper. Processes should never say "I'm so important that I'm disabling PTI". That's crazy talk, and wrong. It's wrong for all the usual reasons - everybody always thinks that _their_ own work is so important and bug-free, and that things like PTI are about protecting all those other imcompetent people. No. Bullshit. Nobody should ever disable PTI for themselves, because nobody is inherently trustworthy. Instead, we have the case of something _external_ saying "this process is so important that it should be started without PTI". Linus