Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp2746470imm; Tue, 4 Sep 2018 09:20:38 -0700 (PDT) X-Google-Smtp-Source: ANB0Vda3KIJNChN7GrM7cYh9WRMxh76kXSXV8TWOCuXiuX4Jvoi1028QSGAtdMuoP9Wt/EbebXQe X-Received: by 2002:a63:d70e:: with SMTP id d14-v6mr32317080pgg.110.1536078038139; Tue, 04 Sep 2018 09:20:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1536078038; cv=none; d=google.com; s=arc-20160816; b=kwv3x854tJmsyVjYjSaGcnZnIGpQMbhn00cf/p3gv8QeZs1tqetaUfDhcUtGYzeNSn DfJ/rtCOH9hnUxFxYx0YBNWxdHB3f8/S5gFLGyBUcbPaAl9RXX5LdRKLWESyFx5iyfq6 +YRAySoPy1a0mP7R2HdSmG7GOGPgUcG4QOoL3+qNsjeUh3kV5xQWgfhS4rZOtWWmaHjc +NVCBpFBqSXNk4McNqmFnL/Pteo9OphEZ0yd+rrb1s35vWmnAvvjoDEIs28VETwhfyxT smX6a+rPiS//3HRWqOp0/ibckRH1qWmFT6TC5ObguTqxb4QP3GVQNbzCJMFr3qpT/NYd rg4g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date :arc-authentication-results; bh=2/92MaEA6g3MHjDMDgu4pJiQRdzWiRno3++a0iZTnKI=; b=MLlSS8MQsvAgC7eo2fz/ivXaE+Icfl1SlFZMT0fQB0dE03Xk4G5RRT75aE9YHe2T8Z Ilx3qvUj9JZLBU5Qb1aSiMghffmGKN9UpBS87UeCtiphMMHIcA5ac2FCABNAzjWl+FPQ Se2WMeuepNtH/GhMQe8FG5uq5SaWBsyxZters+66rCSy3sRkS2MATTJaqUSxSr0toc84 hDynaPlAWFfLu7u2oY/XgEYljTpnKO7R60hhIHmd9DjbnamyjcTYNUV3dMODCmtmTDWR VGrY865iv00NWkTui5UiSR2EqZT974LcaIglxM+T9qH4K0idhJxHfvskD9x0rc9lLhre TrKw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g12-v6si20927811pgk.636.2018.09.04.09.20.22; Tue, 04 Sep 2018 09:20:38 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727278AbeIDUox (ORCPT + 99 others); Tue, 4 Sep 2018 16:44:53 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:57512 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726347AbeIDUox (ORCPT ); Tue, 4 Sep 2018 16:44:53 -0400 Received: from hsi-kbw-5-158-153-52.hsi19.kabel-badenwuerttemberg.de ([5.158.153.52] helo=nanos.tec.linutronix.de) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1fxE2Z-000293-N5; Tue, 04 Sep 2018 18:18:55 +0200 Date: Tue, 4 Sep 2018 18:18:55 +0200 (CEST) From: Thomas Gleixner To: Jiri Kosina cc: Ingo Molnar , Peter Zijlstra , Josh Poimboeuf , Andrea Arcangeli , "Woodhouse, David" , Oleg Nesterov , Tim Chen , linux-kernel@vger.kernel.org, x86@kernel.org Subject: Re: [PATCH v3 2/3] x86/speculation: apply IBPB more strictly to avoid cross-process data leak In-Reply-To: Message-ID: References: User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 4 Sep 2018, Jiri Kosina wrote: > if (tsk && tsk->mm && > tsk->mm->context.ctx_id != last_ctx_id && > - get_dumpable(tsk->mm) != SUID_DUMP_USER) > + ___ptrace_may_access(current, tsk, PTRACE_MODE_IBPB)) Uurgh. If X86_FEATURE_USE_IBPB is not enabled, then the whole __ptrace_may_access() overhead is just done for nothing. > indirect_branch_prediction_barrier(); This really wants to be runtime patched: if (static_cpu_has(X86_FEATURE_USE_IBPB)) stop_speculation(tsk, last_ctx_id); and have an inline for that: static inline void stop_speculation(struct task_struct *tsk, u64 last_ctx_id) { if (tsk && tsk->mm && tsk->mm->context.ctx_id != last_ctx_id && ___ptrace_may_access(current, tsk, PTRACE_MODE_IBPB)) indirect_branch_prediction_barrier(); } which also makes the whole mess readable. Hmm? Thanks, tglx