From: Will Deacon <will.deacon@arm.com>
To: Leif Lindholm <leif.lindholm@linaro.org>
Cc: "ard.biesheuvel@linaro.org" <ard.biesheuvel@linaro.org>,
Catalin Marinas <Catalin.Marinas@arm.com>,
"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"msalter@redhat.com" <msalter@redhat.com>
Subject: Re: [PATCH v2 0/2] arm64: don't call early_*map() post paging_init()
Date: Tue, 6 Jan 2015 13:59:42 +0000 [thread overview]
Message-ID: <20150106135941.GA3484@arm.com> (raw)
In-Reply-To: <1420551673-31416-1-git-send-email-leif.lindholm@linaro.org>
On Tue, Jan 06, 2015 at 01:41:11PM +0000, Leif Lindholm wrote:
> This (tiny) series resolves a fairly serious problem with
> early_ioremap/iounmap/memremap/memunmap on arm64. These functions
> cannot safely be called after paging_init(), but the sanity check
> was not triggering.
>
> As a result, a fixmap entry was incorrectly cleared during
> early_initcalls on arm64 UEFI systems.
>
> 1/2 reworks the arm64 UEFI support code to not attempt these calls
> and
> 2/2 enables the sanity check
>
> Changes since v1:
> - Rebased to v3.19-rc3
> - Added 'Fixes:' tags
> - Reworked 1/2 to restore call to efi_setup_idmap() to the original
> location in the boot process.
Looks reasonable to me; do they need a CC stable, or is this not a problem
that matters in practice?
Will
WARNING: multiple messages have this Message-ID (diff)
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/2] arm64: don't call early_*map() post paging_init()
Date: Tue, 6 Jan 2015 13:59:42 +0000 [thread overview]
Message-ID: <20150106135941.GA3484@arm.com> (raw)
In-Reply-To: <1420551673-31416-1-git-send-email-leif.lindholm@linaro.org>
On Tue, Jan 06, 2015 at 01:41:11PM +0000, Leif Lindholm wrote:
> This (tiny) series resolves a fairly serious problem with
> early_ioremap/iounmap/memremap/memunmap on arm64. These functions
> cannot safely be called after paging_init(), but the sanity check
> was not triggering.
>
> As a result, a fixmap entry was incorrectly cleared during
> early_initcalls on arm64 UEFI systems.
>
> 1/2 reworks the arm64 UEFI support code to not attempt these calls
> and
> 2/2 enables the sanity check
>
> Changes since v1:
> - Rebased to v3.19-rc3
> - Added 'Fixes:' tags
> - Reworked 1/2 to restore call to efi_setup_idmap() to the original
> location in the boot process.
Looks reasonable to me; do they need a CC stable, or is this not a problem
that matters in practice?
Will
next prev parent reply other threads:[~2015-01-06 13:59 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 13:41 [PATCH v2 0/2] arm64: don't call early_*map() post paging_init() Leif Lindholm
2015-01-06 13:41 ` Leif Lindholm
[not found] ` <1420551673-31416-1-git-send-email-leif.lindholm-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-01-06 13:41 ` [PATCH v2 1/2] arm64: don't make early_*map() calls " Leif Lindholm
2015-01-06 13:41 ` Leif Lindholm
[not found] ` <1420551673-31416-2-git-send-email-leif.lindholm-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-01-06 20:35 ` Mark Salter
2015-01-06 20:35 ` Mark Salter
[not found] ` <1420576522.16211.30.camel-SI7Dh15yCUp82hYKe6nXyg@public.gmane.org>
2015-01-07 10:58 ` Will Deacon
2015-01-07 10:58 ` Will Deacon
2015-01-07 13:13 ` Ard Biesheuvel
2015-01-07 13:13 ` Ard Biesheuvel
[not found] ` <CAKv+Gu9NRRFZG0S6oFJqPG1+1O2-SZah4wqoi0YPofL33X3nJw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-01-07 13:31 ` Leif Lindholm
2015-01-07 13:31 ` Leif Lindholm
[not found] ` <20150107133109.GM3827-t77nlHhSwNqAroYi2ySoxKxOck334EZe@public.gmane.org>
2015-01-07 19:03 ` Will Deacon
2015-01-07 19:03 ` Will Deacon
2015-01-06 13:41 ` [PATCH v2 2/2] arm64: call early_ioremap_reset() in paging_init() Leif Lindholm
2015-01-06 13:41 ` Leif Lindholm
2015-01-06 13:59 ` Will Deacon [this message]
2015-01-06 13:59 ` [PATCH v2 0/2] arm64: don't call early_*map() post paging_init() Will Deacon
[not found] ` <20150106135941.GA3484-5wv7dgnIgG8@public.gmane.org>
2015-01-06 14:04 ` Ard Biesheuvel
2015-01-06 14:04 ` Ard Biesheuvel
[not found] ` <CAKv+Gu-nYC1VaJW6ULY0AantA681xZyxqqC+nQq91nj5t7w4OQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-01-06 15:52 ` Leif Lindholm
2015-01-06 15:52 ` Leif Lindholm
[not found] ` <20150106155208.GC3827-t77nlHhSwNqAroYi2ySoxKxOck334EZe@public.gmane.org>
2015-01-06 15:54 ` Ard Biesheuvel
2015-01-06 15:54 ` Ard Biesheuvel
2015-01-06 16:05 ` Will Deacon
2015-01-06 16:05 ` Will Deacon
[not found] ` <20150106160511.GD3484-5wv7dgnIgG8@public.gmane.org>
2015-01-06 16:23 ` Ard Biesheuvel
2015-01-06 16:23 ` Ard Biesheuvel
[not found] ` <CAKv+Gu8nsdCiKM3fOZ6KSMKJ2-1==TyNv8W2Fo6R4jeO3AsgDg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-01-06 19:18 ` Will Deacon
2015-01-06 19:18 ` Will Deacon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150106135941.GA3484@arm.com \
--to=will.deacon@arm.com \
--cc=Catalin.Marinas@arm.com \
--cc=ard.biesheuvel@linaro.org \
--cc=leif.lindholm@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=msalter@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.