From: Sander Eikelenboom <linux@eikelenboom.it>
To: Ingo Molnar <mingo@kernel.org>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
David Vrabel <david.vrabel@citrix.com>,
xen-devel@lists.xen.org, linux-kernel@vger.kernel.org,
x86@kernel.org, Ingo Molnar <mingo.kernel.org@gmail.com>
Subject: Re: Linux 4.4 MW: Boot under Xen fails with CONFIG_DEBUG_WX enabled: RIP: ptdump_walk_pgd_level_core
Date: Wed, 04 Nov 2015 19:16:25 +0100 [thread overview]
Message-ID: <97d7336487eaf2b1cbb521eea12f835c@eikelenboom.it> (raw)
In-Reply-To: <20151104180655.GA9892@gmail.com>
On 2015-11-04 19:06, Ingo Molnar wrote:
> * Stephen Smalley <sds@tycho.nsa.gov> wrote:
>
>> On 11/04/2015 06:55 AM, Sander Eikelenboom wrote:
>> >Hi All,
>> >
>> >I just tried to boot with the current linus mergewindow tree under Xen.
>> >It fails with a kernel panic at boot with the new "CONFIG_DEBUG_WX"
>> >option enabled.
>> >Disabling it makes the kernel boot fine.
>> >
>> >The splat:
>> >[ 18.424241] Freeing unused kernel memory: 1104K (ffffffff822fc000 -
>> >ffffffff82410000)
>> >[ 18.430314] Write protecting the kernel read-only data: 18432k
>> >[ 18.441054] Freeing unused kernel memory: 1144K (ffff880001ae2000 -
>> >ffff880001c00000)
>> >[ 18.447966] Freeing unused kernel memory: 1560K (ffff88000207a000 -
>> >ffff880002200000)
>> >[ 18.453947] BUG: unable to handle kernel paging request at
>> >ffff88055c883000
>> >[ 18.459943] IP: [<ffffffff8105af8e>]
>> >ptdump_walk_pgd_level_core+0x20e/0x440
>> >[ 18.465847] PGD 2212067 PUD 0
>> >[ 18.471564] Oops: 0000 [#1] SMP
>> >[ 18.477248] Modules linked in:
>> >[ 18.482918] CPU: 2 PID: 1 Comm: swapper/0 Not tainted
>> >4.3.0-mw-20151104-linus-doflr+ #1
>> >[ 18.488804] Hardware name: MSI MS-7640/890FXA-GD70 (MS-7640) , BIOS
>> >V1.8B1 09/13/2010
>> >[ 18.494778] task: ffff880059b90000 ti: ffff880059b98000 task.ti:
>> >ffff880059b98000
>> >[ 18.500852] RIP: e030:[<ffffffff8105af8e>] [<ffffffff8105af8e>]
>> >ptdump_walk_pgd_level_core+0x20e/0x440
>
> It would be nice to see which line of code this corresponds to. Doing
> this:
>
> gdb vmlinux
> list *0xffffffff8105af8e
>
> should normally do the trick.
>
> Thanks,
>
> Ingo
Hi Ingo,
(gdb) list *0xffffffff8105af8e
0xffffffff8105af8e is in ptdump_walk_pgd_level_core
(arch/x86/mm/dump_pagetables.c:181).
warning: Source file is more recent than executable.
176 * On 64 bits, sign-extend the 48 bit address to 64 bit
177 */
178 static unsigned long normalize_addr(unsigned long u)
179 {
180 #ifdef CONFIG_X86_64
181 return (signed long)(u << 16) >> 16;
182 #else
183 return u;
184 #endif
185 }
--
Sander
next prev parent reply other threads:[~2015-11-04 18:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 11:55 Sander Eikelenboom
2015-11-04 15:52 ` Stephen Smalley
2015-11-04 18:06 ` Ingo Molnar
2015-11-04 18:16 ` Sander Eikelenboom [this message]
2015-11-04 18:28 ` Sander Eikelenboom
2015-11-04 18:47 ` Stephen Smalley
2015-11-04 20:02 ` Sander Eikelenboom
2015-11-04 23:13 ` [Xen-devel] " Boris Ostrovsky
2015-11-05 9:13 ` Sander Eikelenboom
2015-11-05 13:53 ` Boris Ostrovsky
2015-11-05 14:02 ` Sander Eikelenboom
2015-11-04 20:15 ` Boris Ostrovsky
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=97d7336487eaf2b1cbb521eea12f835c@eikelenboom.it \
--to=linux@eikelenboom.it \
--cc=david.vrabel@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo.kernel.org@gmail.com \
--cc=mingo@kernel.org \
--cc=sds@tycho.nsa.gov \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®