From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965758AbcAURoH (ORCPT ); Thu, 21 Jan 2016 12:44:07 -0500 Received: from out3-smtp.messagingengine.com ([66.111.4.27]:44924 "EHLO out3-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965648AbcAURoE (ORCPT ); Thu, 21 Jan 2016 12:44:04 -0500 Message-Id: <1453398243.2408446.498798962.17B9E6CB@webmail.messagingengine.com> X-Sasl-Enc: NaZZp4RrycG9aAtXwvTiOzcS+eLj15fyRNOM93umNqDN 1453398243 From: suse.dev@fea.st To: linux-kernel@vger.kernel.org Cc: linux-mm@kvack.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-6cda141f Subject: kernel 4.4.0 OOPS: "x86/mm: Found insecure W+X mapping at address ..." Date: Thu, 21 Jan 2016 09:44:03 -0800 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org I'm booting kernel 4.4.x + xen 4.6 -- recently upgraded from kernel 4.3.x, uname -rm 4.4.0-3.g0567b9b-default x86_64 kernel pkgs are from opensuse repos @ http://download.opensuse.org/repositories/Kernel:/stable/standard Post-upgrade, I'm seeing the following OOPS on boot; apparently non-fatal, as the system _does_ subsequently complete boot. There are a couple of prior mentions on LKML, as yet unaddressed https://lkml.org/lkml/2015/11/7/57 https://lkml.org/lkml/2016/1/19/134 as well as on Xen ML http://lists.xen.org/archives/html/xen-devel/2015-11/msg00514.html Here's the trace, Jan 20 17:43:49 x001 kernel: ------------[ cut here ]------------ Jan 20 17:43:49 x001 kernel: WARNING: CPU: 0 PID: 1 at ../arch/x86/mm/dump_pagetables.c:225 note_page+0x5e1/0x780() Jan 20 17:43:49 x001 kernel: x86/mm: Found insecure W+X mapping at address ffff880000000000/0xffff880000000000 Jan 20 17:43:49 x001 kernel: Modules linked in: Jan 20 17:43:49 x001 kernel: CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.4.0-3.g0567b9b-default #1 Jan 20 17:43:49 x001 kernel: Hardware name: Supermicro X10SAT/X10SAT, BIOS 3.0 05/26/2015 Jan 20 17:43:49 x001 kernel: ffffffff81a44e20 ffff880169f57d58 ffffffff8137f639 ffff880169f57da0 Jan 20 17:43:49 x001 kernel: ffff880169f57d90 ffffffff8107d132 ffff880169f57e98 0010000000000027 Jan 20 17:43:49 x001 kernel: 0000000000000004 0000000000000000 0000000000000000 ffff880169f57df0 Jan 20 17:43:49 x001 kernel: Call Trace: Jan 20 17:43:49 x001 kernel: [] try_stack_unwind+0x175/0x190 Jan 20 17:43:49 x001 kernel: [] dump_trace+0x69/0x3a0 Jan 20 17:43:49 x001 kernel: [] show_trace_log_lvl+0x4b/0x60 Jan 20 17:43:49 x001 kernel: [] show_stack_log_lvl+0x10c/0x180 Jan 20 17:43:49 x001 kernel: [] show_stack+0x25/0x50 Jan 20 17:43:49 x001 kernel: [] dump_stack+0x4b/0x72 Jan 20 17:43:49 x001 kernel: [] warn_slowpath_common+0x82/0xc0 Jan 20 17:43:49 x001 kernel: [] warn_slowpath_fmt+0x4c/0x50 Jan 20 17:43:49 x001 kernel: [] note_page+0x5e1/0x780 Jan 20 17:43:49 x001 kernel: [] ptdump_walk_pgd_level_core+0x2ee/0x420 Jan 20 17:43:49 x001 kernel: [] ptdump_walk_pgd_level_checkwx+0x17/0x20 Jan 20 17:43:49 x001 kernel: [] mark_rodata_ro+0xef/0x100 Jan 20 17:43:49 x001 kernel: [] kernel_init+0x1d/0xe0 Jan 20 17:43:49 x001 kernel: [] ret_from_fork+0x3f/0x70 Jan 20 17:43:49 x001 kernel: DWARF2 unwinder stuck at ret_from_fork+0x3f/0x70 Jan 20 17:43:49 x001 kernel: Jan 20 17:43:49 x001 kernel: Leftover inexact backtrace: Jan 20 17:43:49 x001 kernel: [] ? rest_init+0x90/0x90 Jan 20 17:43:49 x001 kernel: ---[ end trace 3cc91a447d30cdcf ]--- Jan 20 17:43:49 x001 kernel: x86/mm: Checked W+X mappings: FAILED, 4090 W+X pages found. No sure what additional info's helpful; let me know specific, and I can provide. Thanks.