From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stable-owner@vger.kernel.org>
Received: from mail.linuxfoundation.org ([140.211.169.12]:60466 "EHLO
        mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1753483AbeDTGp1 (ORCPT
        <rfc822;stable@vger.kernel.org>); Fri, 20 Apr 2018 02:45:27 -0400
Date: Fri, 20 Apr 2018 08:41:29 +0200
From: Greg KH <gregkh@linuxfoundation.org>
To: Jason Andryuk <jandryuk@gmail.com>
Cc: stable@vger.kernel.org
Subject: Re: Request: x86/xen: Delay get_cpu_cap until stack canary is
 established
Message-ID: <20180420064129.GA18464@kroah.com>
References: <CAKf6xptp26JmuagqkyNKbWuDmygqvUJoY694GfXtZKstYPjrxg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAKf6xptp26JmuagqkyNKbWuDmygqvUJoY694GfXtZKstYPjrxg@mail.gmail.com>
Sender: stable-owner@vger.kernel.org
List-ID: <stable.vger.kernel.org>

On Thu, Apr 19, 2018 at 12:40:25PM -0400, Jason Andryuk wrote:
> x86/xen: Delay get_cpu_cap until stack canary is established
> 
> Upstream commit 36104cb9012a82e73c32a3b709257766b16bcd1d
> 
> 32bit Xen domains cannot boot without this patch.  They crash early in
> boot without output because they call into -f-stack-protector code
> without the canary established.  This patch re-orders code to avoid
> that.
> 
> I've been running this patch on 4.14 and would like it applied there.

Now queued up, thanks.

greg k-h