Received: by 10.213.65.68 with SMTP id h4csp850620imn; Sat, 31 Mar 2018 11:31:21 -0700 (PDT) X-Google-Smtp-Source: AIpwx48oyaQBT8kTT1vXHPVSgxvhGXpwVLSCZytd04zR65E+GbPERamkP/vvUDLGxEO7HUmr7AHf X-Received: by 10.98.60.146 with SMTP id b18mr2840493pfk.36.1522521081642; Sat, 31 Mar 2018 11:31:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1522521081; cv=none; d=google.com; s=arc-20160816; b=gMqbuUZqT60Y+X/5Js5yUxXp98sBTQwbaypOM8m2Ali8lFGu6n5b9sDADd7hIZoNSM miFfVNQ1MkzZy1IcX0NzLQt5BQRnFhgLphbLyZa/PbBvUw7gVFsQh19p5ufEHbAdXebh WU/uXQjwef/ZJQsssuoqoAyOPaY5bkD7j8Drw3thM9/JYdAYTX5GyMBiKQ5ib17Ez2q4 27A0TJFvRMn84Wvs09XY2CDFaPRxM+45/PuphpzbxSZ6oLVCm0OW3ya1p+5WpeIXDz2g v4XlN6pdWRLYSuxl+gyYBZQVWtGSjX1W+cf+JoIOcpC5l9lr4/0f4eg/nEKNokPNrRlt Ialw== 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=l7Grwo8zsWd7CcS1932ChRLNrT49YLWp9eYnMHukYiw=; b=Y9uYOQiKI06UE+RN36V5eFtSZCayBnALqWIdPgMvFxJ3Suty3OQwCakBD6oVkOob8M 01YWHg4A9Tkz3KxgrqajD59eXUDs8rdKJMUputLZNokjQ0QJ2moj9Uo7etr6Y/eh34/Q 6BOgO4aQWN9zHRDz5yiO7CjtKl+77NrGwX7OQJrvS3mHJP95eG5uSyV09msPF6vOjTWI zAuh2ddvcg9/HLtMD/S3/py7eqPbx4CtPe0KX5JKKBvMsaGQ55P4OJediPTA/3B2S8cR rRnDDZ9naE71DifYHngpPt7hiIcBUNRlUpI98LL+17V2E4aeLUEbZ9TynxRtz8ri/lWy p40g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=bPigGMkS; 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=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x5si7375225pgb.365.2018.03.31.11.31.07; Sat, 31 Mar 2018 11:31:21 -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=@gmail.com header.s=20161025 header.b=bPigGMkS; 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=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753278AbeCaS3x (ORCPT + 99 others); Sat, 31 Mar 2018 14:29:53 -0400 Received: from mail-lf0-f67.google.com ([209.85.215.67]:41942 "EHLO mail-lf0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753073AbeCaS3v (ORCPT ); Sat, 31 Mar 2018 14:29:51 -0400 Received: by mail-lf0-f67.google.com with SMTP id o102-v6so16064067lfg.8; Sat, 31 Mar 2018 11:29:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=l7Grwo8zsWd7CcS1932ChRLNrT49YLWp9eYnMHukYiw=; b=bPigGMkS+w3W2TiriQ+xdTsvH6mivmcV2nzT0Z4b3fzS7r8ejtBUqPdLBs2yGAcvZo eRGgE6tP/sptboXNnmnhOMLiK+bJ4jIbN/MPAtJZcjc4+9G7XhvaSGU/RLCIugbTm3/P z5llWcbNS0mtTaujWdPz3PaPhN/k/HF13WfxPMmAWXX3D+gqJGOMV7JpRNAYzRaR2680 ImkeensmMfWcv2vhINu00z9TTX0yeEmKHMK/tpsa44xgX7Of07vmbc5snMpgcizGmeii W7LQFH67ecRmGbWUYrTqTyCkMJScMRVbp3eVaZb4tiInD//hQH6J6V7alxrJKvPOonve aXRQ== 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=l7Grwo8zsWd7CcS1932ChRLNrT49YLWp9eYnMHukYiw=; b=TyfwxkkIxBTfUhJsEYtHr8S6ypIbnBMVr37Tk+iC1nNA6B1XApQjuBHOEv2VzWn+B3 q22DO9zMKSVIlzGE38DNt1lgu74MaSQwQlZCoX/Dx0c751YqKlonKyIStakfH6shbz/t WR9Ld/2zHryx6mXSStQ+U8NGTgYrQV1ioz0vC+pwlVDow7S2MHN90gJxjS80FV3i3jfd Vdw0qx1zH7A9Gw1chOfID4CK6IyLVPQ/q4mD7OUUF38GFyCerQvBrFrHZn6C7STsGjpb lXBSqg2Etr9H9fU8K0qEphQ86ulngiyzKw7Ypn+k7G0MMEE32eQCxSfPQDnzslJhkB6a 0JIg== X-Gm-Message-State: ALQs6tBeQlAeOteZmtzyjX8HLkqg+/kNku2Yb8v7hFGUwMJ7OWSTnDMa hTy54lIyI25eFBcwY2Kt/Gw2DYFhZbAStZeuuZs= X-Received: by 10.46.158.19 with SMTP id e19mr2278060ljk.47.1522520989900; Sat, 31 Mar 2018 11:29:49 -0700 (PDT) MIME-Version: 1.0 Received: by 10.46.80.18 with HTTP; Sat, 31 Mar 2018 11:29:49 -0700 (PDT) In-Reply-To: References: <20180319165804.10636-1-jandryuk@gmail.com> From: Jason Andryuk Date: Sat, 31 Mar 2018 14:29:49 -0400 Message-ID: Subject: Re: [PATCH] x86/xen: Delay get_cpu_cap until stack canary is established To: Boris Ostrovsky Cc: Juergen Gross , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , x86@kernel.org, xen-devel@lists.xenproject.org, open list , stable@vger.kernel.org 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 Sat, Mar 31, 2018 at 2:10 PM, Boris Ostrovsky wrote: > On 03/31/2018 01:38 PM, Jason Andryuk wrote: >> On Wed, Mar 21, 2018, 5:12 PM Boris Ostrovsky > > wrote: >> >> On 03/19/2018 12:58 PM, Jason Andryuk wrote: >> > Commit 2cc42bac1c79 ("x86-64/Xen: eliminate W+X mappings") >> introduced a >> > call to get_cpu_cap, which is fstack-protected. This is works on >> x86-64 >> > as commit 4f277295e54c ("x86/xen: init %gs very early to avoid page >> > faults with stack protector") ensures the stack protector is >> configured, >> > but it it did not cover x86-32. >> > >> > Delay calling get_cpu_cap until after xen_setup_gdt has >> initialized the >> > stack canary. Without this, a 32bit PV machine crashes early >> > in boot. >> > (XEN) Domain 0 (vcpu#0) crashed on cpu#0: >> > (XEN) ----[ Xen-4.6.6-xc x86_64 debug=n Tainted: C ]---- >> > (XEN) CPU: 0 >> > (XEN) RIP: e019:[<00000000c10362f8>] >> > >> > And the PV kernel IP corresponds to init_scattered_cpuid_features >> > 0xc10362f8 <+24>: mov %gs:0x14,%eax >> > >> > Fixes 2cc42bac1c79 ("x86-64/Xen: eliminate W+X mappings") >> > >> > Signed-off-by: Jason Andryuk > > >> > >> >> >> Applied to for-linus-4.17 >> >> >> Thanks. If it's not too late, can this be cc: stable? > > We can always try ;-) > > This is 4.15 and 4.16 only, I believe. I'm using this patch on 4.14, so there as well. -Jason