Received: by 10.223.176.46 with SMTP id f43csp1701479wra; Sun, 21 Jan 2018 02:37:25 -0800 (PST) X-Google-Smtp-Source: AH8x22615fnwbFQr/+I2ieAVeA9LBKnYUazHeM7O1x5DsReAQriBF/y7QjkrQokchYkyFJcz4nGZ X-Received: by 2002:a17:902:32a2:: with SMTP id z31-v6mr1920139plb.345.1516531045561; Sun, 21 Jan 2018 02:37:25 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1516531045; cv=none; d=google.com; s=arc-20160816; b=HJNjRG8AOjmUNowyBpCrLq0I/C0UWZ0tI5upTp0BL/5DB9lInV6CojUB4zjzGu6QAW 1ky3QBSASBmh4MSmaAL1+spWBAGhaWVnBxjJRiy+tZekuxqUHnkJwrbmnwpVfs9HDvWQ eGgNdA22OnVNL9wZwWhpMr3Bp7MDrHRC1RLhjB4ziyIqf3wisb3FaSD9CudgzUUSBI3e bDgFE2iBREqfmLNfmV5slhGKHrkYpZBEmwqgK7fJ9ekv8qk9FnqhlGFEcPdz8ZhpaVo+ 1kF/15fQhOFXhS+y85QmpQCOvlQytf4ZlECEi/obWSxdoWo4YAutZAiBmPwIBK6ZPgdu lMfw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=eNn++jeti5O2lhTy/X/eXx9VZRef/8oSnU/Nje76sBw=; b=tdqicdATld4VvqLmWM7DPxbF307mQbEkVIpRN5HzytK8xmpEyxI1wTb974Bzpp2P3b Jx8shxJC1MbRQeA4ufzhjNWLbRS8HNJCp5dVL373Sh7GVDrzCVAuYUY4NQybCNIRROHS J4IYmz2q8IsYQMa2+uOzU3ChwrG2rslgjbE5HG8sixosysi5AA8+NCRU+O2MH+hZaEIM B5tqx4aZuKc0Prmbp6P+sxCQhKm3S7Z52xuyKzFjZXdqVUTGWjELylRruiEd/5fenHv6 KXe+OgM139HsrGyiOGMnzEk/IDQPfvAsVxxSjEgZT3KRfdP4OytWVpOI+QboeibTKsOO 3RWg== 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 h26si12018566pgv.636.2018.01.21.02.37.11; Sun, 21 Jan 2018 02:37:25 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751125AbeAUKgq (ORCPT + 99 others); Sun, 21 Jan 2018 05:36:46 -0500 Received: from mail.linuxfoundation.org ([140.211.169.12]:35514 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750941AbeAUKgp (ORCPT ); Sun, 21 Jan 2018 05:36:45 -0500 Received: from localhost (LFbn-1-12258-90.w90-92.abo.wanadoo.fr [90.92.71.90]) by mail.linuxfoundation.org (Postfix) with ESMTPSA id 8ACB8E55; Sun, 21 Jan 2018 10:36:44 +0000 (UTC) Date: Sun, 21 Jan 2018 11:36:44 +0100 From: Greg Kroah-Hartman To: Ingo Molnar Cc: Linus Torvalds , Gabriel C , Laura Abbott , Tom Lendacky , Borislav Petkov , Peter Zijlstra , Thomas Gleixner , Brijesh Singh , X86 ML , Linux Kernel Mailing List , stable Subject: Re: [PATCH] x86: Use __nostackprotect for sme_encrypt_kernel Message-ID: <20180121103644.GA8717@kroah.com> References: <20180121011402.9557-1-labbott@redhat.com> <5585e5d7-2b9d-85b8-59be-7e6fd79bb33f@gmail.com> <20180121093741.GA5010@kroah.com> <20180121095020.72syevzzeekf7q3x@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180121095020.72syevzzeekf7q3x@gmail.com> User-Agent: Mutt/1.9.2 (2017-12-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Jan 21, 2018 at 10:50:20AM +0100, Ingo Molnar wrote: > > * Greg Kroah-Hartman wrote: > > > On Sat, Jan 20, 2018 at 08:16:31PM -0800, Linus Torvalds wrote: > > > On Sat, Jan 20, 2018 at 5:49 PM, Gabriel C wrote: > > > > > > > > Added stable to CC since the patch series this patch fixes > > > > is in stable-queue. > > > > > > Oh, it wasn't clear from the commit message. But I guess the "Fixes:" > > > tag would have caught Greg's eye regardless. > > > > Ugh, I am _so_ behind in looking at patches that only have a Fixes: tag > > in it and not a "Cc: stable@" tag, due to the recent high-volume of the > > latter. > > > > But they will end up in a mbox that I need to dig out of eventually, but > > it will take time, so if you know you want a patch in a stable release, > > it's much easier to just use the "Cc: stable@" tag please. > > Just to make it easier, please put this upstream fix into -stable: > > 91cfc88c66bf: ("x86: Use __nostackprotect for sme_encrypt_kernel") Thanks, now queued up. > I believe all the prerequisite upstream commits are in -stable already: > > 1303880179e6: x86/mm: Clean up register saving in the __enc_copy() assembly code > bacf6b499e11: x86/mm: Use a struct to reduce parameters for SME PGD mapping > 2b5d00b6c2cd: x86/mm: Centralize PMD flags in sme_encrypt_kernel() > cc5f01e28d6c: x86/mm: Prepare sme_encrypt_kernel() for PAGE aligned encryption > 107cd2532181: x86/mm: Encrypt the initrd earlier for BSP microcode update Yes, those are all there already. greg k-h