stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Request: x86/xen: Delay get_cpu_cap until stack canary is established
@ 2018-04-19 16:40 Jason Andryuk
  2018-04-20  6:41 ` Greg KH
  0 siblings, 1 reply; 2+ messages in thread
From: Jason Andryuk @ 2018-04-19 16:40 UTC (permalink / raw)
  To: stable

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.

Regards,
Jason

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Request: x86/xen: Delay get_cpu_cap until stack canary is established
  2018-04-19 16:40 Request: x86/xen: Delay get_cpu_cap until stack canary is established Jason Andryuk
@ 2018-04-20  6:41 ` Greg KH
  0 siblings, 0 replies; 2+ messages in thread
From: Greg KH @ 2018-04-20  6:41 UTC (permalink / raw)
  To: Jason Andryuk; +Cc: stable

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2018-04-20  6:45 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-04-19 16:40 Request: x86/xen: Delay get_cpu_cap until stack canary is established Jason Andryuk
2018-04-20  6:41 ` Greg KH

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).