All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: kernel list <linux-kernel@vger.kernel.org>,
	sds@tycho.nsa.gov, luto@amacapital.net, arjan@linux.intel.com,
	bp@alien8.de, brgerst@gmail.com, dvlasenk@redhat.com,
	hpa@zytor.com, torvalds@linux-foundation.org, efault@gmx.de,
	peterz@infradead.org, tglx@linutronix.de
Subject: 4.4-rc5: ugly warn on: 5 W+X pages found
Date: Mon, 14 Dec 2015 09:04:03 +0100	[thread overview]
Message-ID: <20151214080403.GA3708@amd> (raw)
In-Reply-To: <20151115070022.GA15417@amd>

Hi!

> Kernel complains:

And now, we are at -rc5, and kernel still complains...

...with a back trace, which is clearly completely useless, and just
there to make it scary and make people report.

Problem is... noone cares for the reports. (-rc0 version below).

Can we get rid of that WARN_ON? If you do care about reports, please
add email address those can be reported to. If you don't... just drop
it.

Hardware is thinkpad x60.

								Pavel

[    3.267542] NX-protecting the kernel data: 5764k
[    3.278325] ------------[ cut here ]------------
[    3.282060] WARNING: CPU: 1 PID: 1 at
arch/x86/mm/dump_pagetables.c:225 note_page+0x5ec/0x790()
[    3.285993] x86/mm: Found insecure W+X mapping at address
ffe69000/0xffe69000
[    3.289991] Modules linked in:
[    3.293995] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.4.0-rc5+
#132
[    3.298178] Hardware name: LENOVO 17097HU/17097HU, BIOS 7BETD8WW
(2.19 ) 03/31/2011
[    3.304343]  00000001 00000000 f5cffeac c42ba698 f5cffed8 f5cffec8
c404059b 000000e1
[    3.308840]  c403cb9c f5cfff50 00000163 00000000 f5cffee0 c40405f6
00000009 f5cffed8
[    3.313419]  c4d3347c f5cffef4 f5cfff1c c403cb9c c4d2c08c 000000e1
c4d3347c ffe69000
[    3.317935] Call Trace:
[    3.322395]  [<c42ba698>] dump_stack+0x41/0x59
[    3.326787]  [<c404059b>] warn_slowpath_common+0x6b/0xa0
[    3.331171]  [<c403cb9c>] ? note_page+0x5ec/0x790
[    3.335522]  [<c40405f6>] warn_slowpath_fmt+0x26/0x30
[    3.339839]  [<c403cb9c>] note_page+0x5ec/0x790
[    3.344154]  [<c403ce9f>] ptdump_walk_pgd_level_core+0x15f/0x240
[    3.348440]  [<c403cfa1>] ptdump_walk_pgd_level_checkwx+0x11/0x20
[    3.352611]  [<c4034fdd>] mark_rodata_ro+0xcd/0xf0
[    3.356677]  [<c4a55c97>] kernel_init+0x17/0xc0
[    3.360702]  [<c4a5c409>] ret_from_kernel_thread+0x21/0x38
[    3.364739]  [<c4a55c80>] ? rest_init+0xa0/0xa0
[    3.368709] ---[ end trace 7121849c40f4a5ba ]---
[    3.372716] x86/mm: Checked W+X mappings: FAILED, 5 W+X pages
found.


> [    5.256044] ------------[ cut here ]------------
> [    5.259267] WARNING: CPU: 0 PID: 1 at
> arch/x86/mm/dump_pagetables.c:225 note_page+0x5ec/0x790()
> [    5.262668] x86/mm: Found insecure W+X mapping at address
> ffe69000/0xffe69000
> [    5.267109] Modules linked in:
> [    5.271403] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.3.0+ #122
> [    5.275679] Hardware name: LENOVO 17097HU/17097HU, BIOS 7BETD8WW
> (2.19 ) 03/31/2011
> [    5.279957]  00000000 00000000 f5cffeac c42b9f18 f5cffed8 f5cffec8
> c404062b 000000e1
> [    5.284387]  c403ca9c f5cfff50 00000163 00000000 f5cffee0 c4040686
> 00000009 f5cffed8
> [    5.288815]  c4d268ac f5cffef4 f5cfff1c c403ca9c c4d1f494 000000e1
> c4d268ac ffe69000
> [    5.293314] Call Trace:
> [    5.297602]  [<c42b9f18>] dump_stack+0x41/0x59
> [    5.301864]  [<c404062b>] warn_slowpath_common+0x6b/0xa0
> [    5.306054]  [<c403ca9c>] ? note_page+0x5ec/0x790
> [    5.310209]  [<c4040686>] warn_slowpath_fmt+0x26/0x30
> [    5.314358]  [<c403ca9c>] note_page+0x5ec/0x790
> [    5.318440]  [<c403cd8f>] ptdump_walk_pgd_level_core+0x14f/0x230
> [    5.322578]  [<c403ce91>] ptdump_walk_pgd_level_checkwx+0x11/0x20
> [    5.326632]  [<c4034ead>] mark_rodata_ro+0xcd/0xf0
> [    5.330625]  [<c4a4aab7>] kernel_init+0x17/0xc0
> [    5.334585]  [<c4a511c9>] ret_from_kernel_thread+0x21/0x38
> [    5.338585]  [<c4a4aaa0>] ? rest_init+0xa0/0xa0
> [    5.342583] ---[ end trace bc9ac0874ad9a058 ]---
> [    5.346630] x86/mm: Checked W+X mappings: FAILED, 5 W+X pages
> found.
> 
> ...I'm not quite sure why it does backtrace, or how to debug this
> one...
> 
> 									Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  parent reply	other threads:[~2015-12-14  8:04 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 ` Pavel Machek [this message]
2015-12-14  8:58   ` 4.4-rc5: ugly warn on: " 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                       ` 4.4.-rc5: lguest causes " Pavel Machek
2015-12-16  2:24                         ` 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=20151214080403.GA3708@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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.