Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp4139546imm; Mon, 20 Aug 2018 10:28:15 -0700 (PDT) X-Google-Smtp-Source: AA+uWPzQUiNL489IGD6jKIvMbey6vNt9jR5wyyOgrku1Jh1KxW6Ld4VB3rjtOv4Az01L9Q7f6gvo X-Received: by 2002:a17:902:33c2:: with SMTP id b60-v6mr46344252plc.11.1534786095533; Mon, 20 Aug 2018 10:28:15 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1534786095; cv=none; d=google.com; s=arc-20160816; b=zVAQxmnEdjM5X2RJd0wOF7B5e8n72xBjFuHsyq30gbXFrKI7nX/XVLnrs+Ply8w+Q3 4S4DGt9f0rE9cV1CUGXFpb/GnUzcPrfSTkKvHGacvisl29C11WCEa19eTy/yp/dD1H9L 9oianfTDo2N98uKyjpCgKW5fmlreNsv4Dsn028+bqepsEQzVDJfaePc1JBSlXAJffT7Y Y5YhHuh3GByAbY030brFVDKxj9XmhvHpCbExxojXKmzGfeIT4WUzcJDt/6RmqQstUqsY AH+ZAWnOkRlPDEDsvcYVzCfCQWr5Xp8UwHQ4vZAJWBgz7Wyj7fAL/5e25etMEdfxfT3y s/7g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=v+k+o1T0cZ9w0718XRpCNDH2s4NkFEzOI5V8LWnkCwU=; b=J8YlOGzIJnkrbqndAXelK0l66P1vgeEighyS/tEavNdUuh+bh50M2nBHbADpg9xn5e f8ledyY3Es7f1dHITLW0Tbq80svVd0QDt3BuIxnhhvqUrJXH0yWkpJAPSiuuryOFCae3 Zh0UJ8dVj2LhQwCp7zTyJ4/nlcH4dr1V6iFAxV99JLZqBVhnXVWdc00qsYmLhdF6dkGA NRqEXXEnFaeeTZq6rKBrDjR5ccPJh9ezn0s94tGuCZTLaTXKScUSbV/7yTPJxpbahq79 duwv3O33TPFzRcvfoXeggNBDvTxYjCNd5QaFVLcbPeQxnZDAOFUTrrA8okqMYeQCnFFq Clzw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=eew4t0Wj; 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=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id m9-v6si9793193pga.456.2018.08.20.10.28.00; Mon, 20 Aug 2018 10:28:15 -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; dkim=pass header.i=@google.com header.s=20161025 header.b=eew4t0Wj; 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=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727384AbeHTTis (ORCPT + 99 others); Mon, 20 Aug 2018 15:38:48 -0400 Received: from mail-oi0-f67.google.com ([209.85.218.67]:41167 "EHLO mail-oi0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726024AbeHTTis (ORCPT ); Mon, 20 Aug 2018 15:38:48 -0400 Received: by mail-oi0-f67.google.com with SMTP id k12-v6so26796446oiw.8 for ; Mon, 20 Aug 2018 09:22:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=v+k+o1T0cZ9w0718XRpCNDH2s4NkFEzOI5V8LWnkCwU=; b=eew4t0WjgPTc9zJOhkIFxkEwXyfCLlKC8ygLJ5oheX7noKAMIdolChE+jc3av4ipuG BQ8Ty6mflK8JbCLZyyvzWZHabt1vpxZIYKA3vCQY8DsVWV2FN8LYYV1H3bAlddXKwgbH 8oH6TFS9TFjSUp2sCTvZMVZUkXndH7nslLMQolc1nKPQFfLlHTwQ0OdEw571sYmLlMHR 84T/08rhNhx8OjB80gD7m02QeU/ye9Kt9gaOvFP8y0R4xK7dIcxVor98zYumwy5g8jPk 0AHfX2K05i9GWeHJr6AlyN84/G7pKoCyHwG2WJ2L+nCFQfKpqXdWW6I/IrpoXgoqOtGc zYAQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=v+k+o1T0cZ9w0718XRpCNDH2s4NkFEzOI5V8LWnkCwU=; b=kOPHhssTUBrIAIdS9FCdiycC3+9F/QT/nLri2XwumhFOL7tzvO5I2eVcZM852Cy7Tj V4xN+KlV9wmcw4z3jbjJ97rLoqWXSGgfx1B1O3xOQAS/LzCKNtolLtxyETaXjicpT/4j 5/wlk6Gh3coGKjbSpAazOxmnDNr/g9FO8Jj9/gBp43eB9clSu9WSbxf8svqYlJPcuhgw IOmVZLp3MTX6ZzmV0O/7sMsFa1gSuI710hah4y3wyEFohp3yO8I7t8Ide+KEE1nMUrHu EeNf8ewq4W77rJPdTmbXZz9/UnPGqI+f61p58MpcG2+2TxGhS5rlPV0srvh2aejJodgp QHJQ== X-Gm-Message-State: AOUpUlEAkoE+2q97aa/wNzK6bEyz6ASqYUbZ//Xxj8Szh95oSbDxR6dK E3er3b/GipryftNn1NYa6CX/AU+GMbDk27RvJ6ZSkw== X-Received: by 2002:aca:4141:: with SMTP id o62-v6mr15599309oia.24.1534782150415; Mon, 20 Aug 2018 09:22:30 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:ac9:3408:0:0:0:0:0 with HTTP; Mon, 20 Aug 2018 09:22:29 -0700 (PDT) In-Reply-To: References: <20180807222535.143193-1-jmattson@google.com> From: Jim Mattson Date: Mon, 20 Aug 2018 09:22:29 -0700 Message-ID: Subject: Re: [PATCH] x86/spectre: Expand test for vulnerability to empty RSB exploits To: Thomas Gleixner Cc: Ingo Molnar , "H. Peter Anvin" , "the arch/x86 maintainers" , Borislav Petkov , Konrad Rzeszutek Wilk , David Woodhouse , LKML , Fred Jacobs , Peter Shier Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Aug 20, 2018 at 9:00 AM, Thomas Gleixner wrote: > > On Tue, 7 Aug 2018, Jim Mattson wrote: > > > Skylake-era Intel CPUs are vulnerable to exploits of empty RSB > > conditions. On hardware, platform vulnerability can be determined > > simply by checking the processor's DisplayModel/DisplayFamily > > signature. However, when running in a VM, the operating system should > > also query IA32_ARCH_CAPABILITIES.RSBA[bit 2], a synthetic bit that > > can be set by a hypervisor to indicate that the VM might run on a > > vulnerable physical processor, regardless of the > > DisplayModel/DisplayFamily reported by CPUID. > > > > Note that IA32_ARCH_CAPABILITIES.RSBA[bit 2] is always clear on > > hardware, so the DisplayModel/DisplayFamily check is still required. > > > > For all of the details, see the Intel white paper, "Retpoline: A > > Branch Target Injection Mitigation" (document number 337131-001), > > section 5.3: Virtual Machine CPU Identification. > > > > Signed-off-by: Jim Mattson > > Reviewed-by: Peter Shier > > That has been superseeded by: > > fdf82a7856b3 ("x86/speculation: Protect against userspace-userspace spectreRSB") > > right? At least it does not apply anymore... Right. It doesn't appear that Skylake CPUs get any special treatment any more.