From: Pavel Machek <pavel@ucw.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>, rusty@rustcorp.com.au
Cc: Andy Lutomirski <luto@amacapital.net>,
Arjan van de Ven <arjan@linux.intel.com>,
Borislav Petkov <bp@alien8.de>,
kernel list <linux-kernel@vger.kernel.org>,
Stephen Smalley <sds@tycho.nsa.gov>,
Brian Gerst <brgerst@gmail.com>,
Denys Vlasenko <dvlasenk@redhat.com>, Peter Anvin <hpa@zytor.com>,
Mike Galbraith <efault@gmx.de>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: 4.4.-rc5: lguest causes ugly warn on: 5 W+X pages found
Date: Tue, 15 Dec 2015 22:12:31 +0100 [thread overview]
Message-ID: <20151215211231.GA6752@amd> (raw)
In-Reply-To: <20151215205835.GA3522@amd>
Hi!
> > or similar?
> >
> > The above is entirely untested. Maybe it doesn't compile. Or
> > boot. Or work.
>
> Well, with two extra spaces at each line, it does not apply :-).
>
> I applied it by hand, and the output is:
>
> [ 0.000000] MTRR variable ranges enabled:
...> [ 0.000000] BRK [0x0566c000, 0x0566cfff] PGTABLE
>
> I'll take a look if I can figure out what it means...
Wait, there's more in the log.
[ 1.952146] Bluetooth: HCI UART protocol H4 registered
[ 1.954335] Bluetooth: HCI UART protocol BCSP registered
[ 1.956750] usbcore: registered new interface driver btusb
[ 1.958953] ------------[ cut here ]------------
[ 1.961149] WARNING: CPU: 1 PID: 1 at
./arch/x86/include/asm/pgtable.h:357
vmap_page_range_noflush+0x1f0/0x280()
[ 1.963511] Modules linked in:
[ 1.965849] CPU: 1 PID: 1 Comm: swapper/0 Tainted: G W
4.4.0-rc5+ #137
[ 1.968230] Hardware name: LENOVO 17097HU/17097HU, BIOS 7BETD8WW
(2.19 ) 03/31/2011
[ 1.970593] 00000001 00000000 f5cffe64 c42baaf8 00000000 f5cffe80
c404066b 00000165
[ 1.973103] c40fbe70 00000163 00000000 00000000 f5cffe90 c404070f
00000009 00000000
[ 1.975670] f5cffee0 c40fbe70 c4f88348 00000000 ffe6dfff ffe6e000
c4f8a018 ffe6dfff
[ 1.978304] Call Trace:
[ 1.980882] [<c42baaf8>] dump_stack+0x41/0x59
[ 1.983464] [<c404066b>] warn_slowpath_common+0x6b/0xa0
[ 1.986053] [<c40fbe70>] ? vmap_page_range_noflush+0x1f0/0x280
[ 1.988625] [<c404070f>] warn_slowpath_null+0xf/0x20
[ 1.991154] [<c40fbe70>] vmap_page_range_noflush+0x1f0/0x280
[ 1.993676] [<c40fbf2b>] map_vm_area+0x2b/0x40
[ 1.996153] [<c4f2c795>] init+0xf8/0x1a4
[ 1.998591] [<c4f2c69d>] ? edac_init+0x67/0x67
[ 2.001014] [<c4000442>] do_one_initcall+0xc2/0x1c0
[ 2.003391] [<c4f044e3>] ? initcall_blacklist+0x97/0x97
[ 2.005815] [<c4f044e3>] ? initcall_blacklist+0x97/0x97
[ 2.008161] [<c4051546>] ?
__usermodehelper_set_disable_depth+0x36/0x40
[ 2.010518] [<c407d4a6>] ? up_write+0x16/0x40
[ 2.012817] [<c4f04ba3>] kernel_init_freeable+0xf0/0x16d
[ 2.015078] [<c4f04ba3>] ? kernel_init_freeable+0xf0/0x16d
[ 2.017386] [<c4a4d9c8>] kernel_init+0x8/0xc0
[ 2.019661] [<c4a54149>] ret_from_kernel_thread+0x21/0x38
[ 2.021932] [<c4a4d9c0>] ? rest_init+0xa0/0xa0
[ 2.024168] ---[ end trace e117245cd61feaf2 ]---
[ 2.026383] lguest: mapped switcher at ffe69000
[ 2.028958] sdhci: Secure Digital Host Controller Interface driver
...which I don't understand; did not we say warn on _once_?
... Um. But I think we have a winner: "lguest: mapped switcher at
ffe69000".
Rusty, does the switcher need to be W+X?
And yes, I have lguest enabled, not sure why.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2015-12-15 21:12 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-15 7:00 4.4-rc0: 5 W+X pages found Pavel Machek
2015-11-23 14:37 ` Mihai Donțu
2015-12-08 21:19 ` Kees Cook
2015-12-09 0:10 ` Dave Jones
2015-12-09 19:33 ` Mihai Donțu
2015-12-14 8:04 ` 4.4-rc5: ugly warn on: " Pavel Machek
2015-12-14 8:58 ` Borislav Petkov
2015-12-14 9:07 ` Pavel Machek
2015-12-14 9:15 ` Borislav Petkov
2015-12-14 19:18 ` Linus Torvalds
2015-12-14 20:26 ` Pavel Machek
2015-12-14 21:02 ` Andy Lutomirski
2015-12-14 21:24 ` Arjan van de Ven
2015-12-14 22:25 ` Andy Lutomirski
2015-12-15 9:40 ` Pavel Machek
2015-12-15 17:45 ` Linus Torvalds
2015-12-15 18:30 ` Borislav Petkov
2015-12-15 19:06 ` Linus Torvalds
2015-12-15 19:15 ` Borislav Petkov
2015-12-15 18:40 ` Andy Lutomirski
2015-12-15 19:08 ` Linus Torvalds
2015-12-15 20:58 ` Pavel Machek
2015-12-15 21:12 ` Pavel Machek [this message]
2015-12-16 2:24 ` 4.4.-rc5: lguest causes " Rusty Russell
2015-12-16 8:10 ` Pavel Machek
2015-12-15 21:33 ` 4.4-rc5: " Borislav Petkov
2015-12-15 22:07 ` Pavel Machek
2015-12-15 22:15 ` Borislav Petkov
2015-12-15 7:56 ` Pavel Machek
2015-12-15 8:09 ` [PATCH 0/2] x86/mm: A _PAGE_NX fixlet and a kmap cleanup Andy Lutomirski
2015-12-15 8:09 ` [PATCH 1/2] x86_32/mm: Set NX in __supported_pte_mask before enabling paging Andy Lutomirski
2015-12-15 8:09 ` [PATCH 2/2] x86/mm: Make kmap_prot into a #define Andy Lutomirski
2016-01-19 9:26 ` [PATCH 0/2] x86/mm: A _PAGE_NX fixlet and a kmap cleanup Ingo Molnar
2016-01-19 19:44 ` Andy Lutomirski
2015-12-15 13:26 ` 4.4-rc5: ugly warn on: 5 W+X pages found Arjan van de Ven
2015-12-15 14:08 ` Pavel Machek
2015-12-15 16:28 ` H. Peter Anvin
2015-12-15 17:45 ` Pavel Machek
2015-12-14 12:29 ` Pavel Machek
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=20151215211231.GA6752@amd \
--to=pavel@ucw.cz \
--cc=arjan@linux.intel.com \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=dvlasenk@redhat.com \
--cc=efault@gmx.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=peterz@infradead.org \
--cc=rusty@rustcorp.com.au \
--cc=sds@tycho.nsa.gov \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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