From: Matt Fleming <matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
To: Ingo Molnar <mingo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>,
"H . Peter Anvin" <hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
Cc: linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
"Josh Triplett" <josh-iaAMLnmF4UmaiuxdJuQwMA@public.gmane.org>,
"Sai Praneeth Prakhya"
<sai.praneeth.prakhya-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
"Borislav Petkov" <bp-l3A5Bk7waGM@public.gmane.org>,
"Môshe van der Sterre" <me-A/3C56C7qwM@public.gmane.org>
Subject: Re: [PATCH] x86/efi-bgrt: Replace early_memremap() with memremap()
Date: Mon, 4 Jan 2016 13:12:15 +0000 [thread overview]
Message-ID: <20160104131215.GA2840@codeblueprint.co.uk> (raw)
In-Reply-To: <1450707172-12561-1-git-send-email-matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
On Mon, 21 Dec, at 02:12:52PM, Matt Fleming wrote:
> Môshe reported the following warning triggered on his machine since
> commit 50a0cb565246 ("x86/efi-bgrt: Fix kernel panic when mapping BGRT
> data"),
>
> [ 0.026936] ------------[ cut here ]------------
> [ 0.026941] WARNING: CPU: 0 PID: 0 at mm/early_ioremap.c:137 __early_ioremap+0x102/0x1bb()
> [ 0.026941] Modules linked in:
> [ 0.026944] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.4.0-rc1 #2
> [ 0.026945] Hardware name: Dell Inc. XPS 13 9343/09K8G1, BIOS A05 07/14/2015
> [ 0.026946] 0000000000000000 900f03d5a116524d ffffffff81c03e60 ffffffff813a3fff
> [ 0.026948] 0000000000000000 ffffffff81c03e98 ffffffff810a0852 00000000d7b76000
> [ 0.026949] 0000000000000000 0000000000000001 0000000000000001 000000000000017c
> [ 0.026951] Call Trace:
> [ 0.026955] [<ffffffff813a3fff>] dump_stack+0x44/0x55
> [ 0.026958] [<ffffffff810a0852>] warn_slowpath_common+0x82/0xc0
> [ 0.026959] [<ffffffff810a099a>] warn_slowpath_null+0x1a/0x20
> [ 0.026961] [<ffffffff81d8c395>] __early_ioremap+0x102/0x1bb
> [ 0.026962] [<ffffffff81d8c602>] early_memremap+0x13/0x15
> [ 0.026964] [<ffffffff81d78361>] efi_bgrt_init+0x162/0x1ad
> [ 0.026966] [<ffffffff81d778ec>] efi_late_init+0x9/0xb
> [ 0.026968] [<ffffffff81d58ff5>] start_kernel+0x46f/0x49f
> [ 0.026970] [<ffffffff81d58120>] ? early_idt_handler_array+0x120/0x120
> [ 0.026972] [<ffffffff81d58339>] x86_64_start_reservations+0x2a/0x2c
> [ 0.026974] [<ffffffff81d58485>] x86_64_start_kernel+0x14a/0x16d
> [ 0.026977] ---[ end trace f9b3812eb8e24c58 ]---
> [ 0.026978] efi_bgrt: Ignoring BGRT: failed to map image memory
>
> early_memremap() has an upper limit on the size of mapping it can
> handle which is ~200KB. Clearly the BGRT image on Môshe's machine is
> much larger than that.
>
> There's actually no reason to restrict ourselves to using the early_*
> version of memremap() - the ACPI BGRT driver is invoked late enough in
> boot that we can use the standard version, with the benefit that the
> late version allows mappings of arbitrary size.
>
> Reported-by: Môshe van der Sterre <me-A/3C56C7qwM@public.gmane.org>
> Tested-by: Môshe van der Sterre <me-A/3C56C7qwM@public.gmane.org>
> Cc: Josh Triplett <josh-iaAMLnmF4UmaiuxdJuQwMA@public.gmane.org>
> Cc: Sai Praneeth Prakhya <sai.praneeth.prakhya-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
> Cc: Borislav Petkov <bp-l3A5Bk7waGM@public.gmane.org>
> Signed-off-by: Matt Fleming <matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
> ---
> arch/x86/platform/efi/efi-bgrt.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
Ping? Could someone please pick this up for the 'x86/efi' branch? It
fixes a bug in 50a0cb565246 ("x86/efi-bgrt: Fix kernel panic when
mapping BGRT data").
WARNING: multiple messages have this Message-ID (diff)
From: Matt Fleming <matt@codeblueprint.co.uk>
To: Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H . Peter Anvin" <hpa@zytor.com>
Cc: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
"Josh Triplett" <josh@joshtriplett.org>,
"Sai Praneeth Prakhya" <sai.praneeth.prakhya@intel.com>,
"Borislav Petkov" <bp@suse.de>,
"Môshe van der Sterre" <me@moshe.nl>
Subject: Re: [PATCH] x86/efi-bgrt: Replace early_memremap() with memremap()
Date: Mon, 4 Jan 2016 13:12:15 +0000 [thread overview]
Message-ID: <20160104131215.GA2840@codeblueprint.co.uk> (raw)
In-Reply-To: <1450707172-12561-1-git-send-email-matt@codeblueprint.co.uk>
On Mon, 21 Dec, at 02:12:52PM, Matt Fleming wrote:
> Môshe reported the following warning triggered on his machine since
> commit 50a0cb565246 ("x86/efi-bgrt: Fix kernel panic when mapping BGRT
> data"),
>
> [ 0.026936] ------------[ cut here ]------------
> [ 0.026941] WARNING: CPU: 0 PID: 0 at mm/early_ioremap.c:137 __early_ioremap+0x102/0x1bb()
> [ 0.026941] Modules linked in:
> [ 0.026944] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.4.0-rc1 #2
> [ 0.026945] Hardware name: Dell Inc. XPS 13 9343/09K8G1, BIOS A05 07/14/2015
> [ 0.026946] 0000000000000000 900f03d5a116524d ffffffff81c03e60 ffffffff813a3fff
> [ 0.026948] 0000000000000000 ffffffff81c03e98 ffffffff810a0852 00000000d7b76000
> [ 0.026949] 0000000000000000 0000000000000001 0000000000000001 000000000000017c
> [ 0.026951] Call Trace:
> [ 0.026955] [<ffffffff813a3fff>] dump_stack+0x44/0x55
> [ 0.026958] [<ffffffff810a0852>] warn_slowpath_common+0x82/0xc0
> [ 0.026959] [<ffffffff810a099a>] warn_slowpath_null+0x1a/0x20
> [ 0.026961] [<ffffffff81d8c395>] __early_ioremap+0x102/0x1bb
> [ 0.026962] [<ffffffff81d8c602>] early_memremap+0x13/0x15
> [ 0.026964] [<ffffffff81d78361>] efi_bgrt_init+0x162/0x1ad
> [ 0.026966] [<ffffffff81d778ec>] efi_late_init+0x9/0xb
> [ 0.026968] [<ffffffff81d58ff5>] start_kernel+0x46f/0x49f
> [ 0.026970] [<ffffffff81d58120>] ? early_idt_handler_array+0x120/0x120
> [ 0.026972] [<ffffffff81d58339>] x86_64_start_reservations+0x2a/0x2c
> [ 0.026974] [<ffffffff81d58485>] x86_64_start_kernel+0x14a/0x16d
> [ 0.026977] ---[ end trace f9b3812eb8e24c58 ]---
> [ 0.026978] efi_bgrt: Ignoring BGRT: failed to map image memory
>
> early_memremap() has an upper limit on the size of mapping it can
> handle which is ~200KB. Clearly the BGRT image on Môshe's machine is
> much larger than that.
>
> There's actually no reason to restrict ourselves to using the early_*
> version of memremap() - the ACPI BGRT driver is invoked late enough in
> boot that we can use the standard version, with the benefit that the
> late version allows mappings of arbitrary size.
>
> Reported-by: Môshe van der Sterre <me@moshe.nl>
> Tested-by: Môshe van der Sterre <me@moshe.nl>
> Cc: Josh Triplett <josh@joshtriplett.org>
> Cc: Sai Praneeth Prakhya <sai.praneeth.prakhya@intel.com>
> Cc: Borislav Petkov <bp@suse.de>
> Signed-off-by: Matt Fleming <matt@codeblueprint.co.uk>
> ---
> arch/x86/platform/efi/efi-bgrt.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
Ping? Could someone please pick this up for the 'x86/efi' branch? It
fixes a bug in 50a0cb565246 ("x86/efi-bgrt: Fix kernel panic when
mapping BGRT data").
next prev parent reply other threads:[~2016-01-04 13:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-21 14:12 [PATCH] x86/efi-bgrt: Replace early_memremap() with memremap() Matt Fleming
2015-12-21 14:12 ` Matt Fleming
[not found] ` <1450707172-12561-1-git-send-email-matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
2015-12-21 20:07 ` Josh Triplett
2015-12-21 20:07 ` Josh Triplett
2016-01-04 13:12 ` Matt Fleming [this message]
2016-01-04 13:12 ` Matt Fleming
2016-01-06 17:33 ` [tip:x86/efi] " tip-bot for Matt Fleming
-- strict thread matches above, loose matches on Subject: below --
2017-12-01 8:35 [PATCH] " Ghannam, Yazen
2017-12-01 16:15 ` Greg KH
2017-12-01 16:25 ` Ghannam, Yazen
2017-12-02 8:15 ` Greg KH
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=20160104131215.GA2840@codeblueprint.co.uk \
--to=matt-mf/unelci9gs6ibeejttw/xrex20p6io@public.gmane.org \
--cc=bp-l3A5Bk7waGM@public.gmane.org \
--cc=hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org \
--cc=josh-iaAMLnmF4UmaiuxdJuQwMA@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=me-A/3C56C7qwM@public.gmane.org \
--cc=mingo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=sai.praneeth.prakhya-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org \
/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.