From: Dave Hansen <dave.hansen@linux.intel.com>
To: Juerg Haefliger <juerg.haefliger@canonical.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Cc: mingo@kernel.org, tglx@linutronix.de, peterz@infradead.org,
hughd@google.com, luto@kernel.org
Subject: Re: KAISER: kexec triggers a warning
Date: Fri, 1 Dec 2017 07:31:36 -0800 [thread overview]
Message-ID: <84c7dd7d-5e01-627e-6f26-5c1e30a87683@linux.intel.com> (raw)
In-Reply-To: <03012d01-4d04-1d58-aa93-425f142f9292@canonical.com>
On 12/01/2017 05:52 AM, Juerg Haefliger wrote:
> Loading a kexec kernel using today's linux-tip master with KAISER=y
> triggers the following warning:
>
> [ 18.054017] ------------[ cut here ]------------
> [ 18.054024] WARNING: CPU: 0 PID: 1183 at
> ./arch/x86/include/asm/pgtable_64.h:258 native_set_p4d+0x5f/0x80
> [ 18.054025] Modules linked in: nls_utf8 isofs ppdev nls_iso8859_1
> kvm_intel kvm irqbypass input_leds serio_raw i2c_piix4 parport_pc
> parport qemu_fw_cfg mac_hid 9p fscache ib_iser rdma_cm iw_cm ib_cm
This is kexec is messing with PTEs that map the kernel, which is OK for
kexec to do. The warning is harmless.
The only question is whether we want to preserve _some_ kind of warning
there, or just axe it entirely.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-12-01 15:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 13:52 Juerg Haefliger
2017-12-01 15:18 ` Baoquan He
2017-12-01 15:27 ` Borislav Petkov
2017-12-04 1:52 ` Baoquan He
2017-12-01 15:31 ` Dave Hansen [this message]
2017-12-01 15:37 ` Borislav Petkov
2017-12-01 16:38 ` Eduardo Valentin
2017-12-01 17:03 ` Borislav Petkov
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=84c7dd7d-5e01-627e-6f26-5c1e30a87683@linux.intel.com \
--to=dave.hansen@linux.intel.com \
--cc=hughd@google.com \
--cc=juerg.haefliger@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox