Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp864613imu; Tue, 20 Nov 2018 08:06:34 -0800 (PST) X-Google-Smtp-Source: AFSGD/WNDakQogOal8tfz4KJrRcP0AeBS8/caPHZO+vLi6oCff8kxAyQiWJPE5HQngeVcokbU7uo X-Received: by 2002:a63:c503:: with SMTP id f3mr2333421pgd.431.1542729994199; Tue, 20 Nov 2018 08:06:34 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1542729994; cv=none; d=google.com; s=arc-20160816; b=Bl8FJLDkRbZPLjTwToJ0x4oZpTIrxVry4StG1xo5wiHy58/wEElwQs6kae3MGR+gb/ eavL1SEKhgcbpygW/qfNgwRzetXcr0X25/sAVUPtKsPNLMHrJlB1uyYcDOxq2MQmWnG1 1bpqYYV+CXGhGhkclz+6eI6rNHIgEYz06mJjfxvdjyd65eUOd3ZJrYEIal4RkcYwUpAA EtDBZYTdd2gbaGHKML+rvWRlDWIoandOmOYzvXDA44oOhMkUy+A22oc6oNWJHihY1uH5 +kh5LFGgBZ+7GTpe4m5xWl9QKK7mFEM/LmB1J1HFT0iS67aP2LZkwwGlgyaH+FwPGvV8 d2+w== 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; bh=0uNQxt4Pwoe3B90xW0/GMjnInfwtQ5lP3g7mP9TMXnI=; b=BVHCy58WaNf+sUJtXxO17x53SrSi5V+43xwmTz+VHUjTRTG/150/aQIIFeF/gwn1rO 5qqL/dVPf6GCsuJBY8walI/uK0Q9nK8KBRG9zYKtiBJ0IX+CIbPZA7YmC8lnwZIEoRqf DVD/plM9XaIlzKv1Zb+g/efoKvYJUSrHkbHDJWXkfILIOZjFkUJzHwurVXwNMNPXVbIq xsj+xUt+csqbBuVzkzVpYlmf7NSTnXjJeIIF0AdKse39QZZYOzxwm7cfLp4OLPiY5Flh aWSMGOvn8tXhhyKj8889qfQ9PrLtbLUUtseOMFAMs3KPOfykYI/rzSHdkkcxXg5N9Gil /XGQ== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id n17si42121240pgj.191.2018.11.20.08.06.17; Tue, 20 Nov 2018 08:06:34 -0800 (PST) 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729930AbeKUB4o (ORCPT + 99 others); Tue, 20 Nov 2018 20:56:44 -0500 Received: from mx2.suse.de ([195.135.220.15]:44720 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725935AbeKUB4o (ORCPT ); Tue, 20 Nov 2018 20:56:44 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 02A49AD93; Tue, 20 Nov 2018 15:27:03 +0000 (UTC) Date: Tue, 20 Nov 2018 16:27:01 +0100 (CET) From: Jiri Kosina To: Arjan van de Ven cc: Linus Torvalds , Thomas Gleixner , Peter Zijlstra , Josh Poimboeuf , Andrea Arcangeli , David Woodhouse , Andi Kleen , Tim Chen , "Schaufler, Casey" , Linux List Kernel Mailing , the arch/x86 maintainers , "stable@vger.kernel.org" Subject: Re: Re: STIBP by default.. Revert? In-Reply-To: <51127fd4-5dcc-b2b9-4873-72098d2a77d9@linux.intel.com> Message-ID: References: <51127fd4-5dcc-b2b9-4873-72098d2a77d9@linux.intel.com> User-Agent: Alpine 2.21 (LSU 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 Mon, 19 Nov 2018, Arjan van de Ven wrote: > In the documentation, AMD officially recommends against this by default, > and I can speak for Intel that our position is that as well: this really > must not be on by default. Thanks for pointing to the AMD doc, it's indeed clearly stated there. Is there any chance this could perhaps be added to Intel documentation as well, so that we avoid cases like this in the future? The revision 3.0 of Intel doc from may 2018 [1] I am always looking into doesn't say anything discouraging about STIBP to me. [1] https://software.intel.com/security-software-guidance/api-app/sites/default/files/336996-Speculative-Execution-Side-Channel-Mitigations.pdf?_gclid=5b78f4d130faf8.22277271-5b78f4d130fb70.17467890&_utm_source=xakep&_utm_campaign=mention177777&_utm_medium=inline&_utm_content=lnk223716354570 Thanks, -- Jiri Kosina SUSE Labs