linux-kernel - Re: KAISER: kexec triggers a warning

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 1 Dec 2017 07:31:36 -0800
From:   Dave Hansen <dave.hansen@...ux.intel.com>
To:     Juerg Haefliger <juerg.haefliger@...onical.com>,
        linux-kernel@...r.kernel.org, linux-mm@...ck.org
Cc:     mingo@...nel.org, tglx@...utronix.de, peterz@...radead.org,
        hughd@...gle.com, luto@...nel.org
Subject: Re: KAISER: kexec triggers a warning

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.