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]:50654 "EHLO
        mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751048AbdADN5l (ORCPT
        <rfc822;stable@vger.kernel.org>); Wed, 4 Jan 2017 08:57:41 -0500
Date: Wed, 4 Jan 2017 14:58:00 +0100
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Matthias Brugger <mbrugger@suse.com>
Cc: stable@vger.kernel.org, Geoff Levand <geoff@infradead.org>,
        Mark Rutland <mark.rutland@arm.com>
Subject: Re: v4.8: arm64 fix kexec
Message-ID: <20170104135800.GA7299@kroah.com>
References: <d14ff0d6-6d63-0186-8dbb-c6064e3a7686@suse.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <d14ff0d6-6d63-0186-8dbb-c6064e3a7686@suse.com>
Sender: stable-owner@vger.kernel.org
List-ID: <stable.vger.kernel.org>

On Wed, Dec 14, 2016 at 08:20:27PM +0100, Matthias Brugger wrote:
> Hi all,
> 
> kexec on arm64 is broken in v4.8.y because in /proc/iomem "nomap" regions,
> like UEFI runtime services code/data, are marked as "System RAM".
> On seattle this leads to the fact, that kexec from kexec-tools loads the
> kernel and the initrd in a memory region which should be ""reserved". This
> breaks kexec on the system.
> 
> commit
> e7cd190385d1 ("arm64: mark reserved memblock regions explicitly in iomem")
> 
> Fixes this and should be added to v4.8 stable tree.

Now queued up, thanks.

greg k-h