From: Meelis Roos <mroos@linux.ee>
To: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: 4.15-rc9 new insecure W+X mapping warning
Date: Mon, 26 Feb 2018 11:29:17 +0200 (EET) [thread overview]
Message-ID: <alpine.LRH.2.21.1802261127370.4893@math.ut.ee> (raw)
In-Reply-To: <alpine.LRH.2.21.1801242127140.27627@math.ut.ee>
> This is Intel SE7520JR22S mainboard with 2 64-bit P4 xeons. Earlier
> kernels up to 4.14 have had W+X checking on but found nothing. Now I
> tried 4.15.0-rc9-00023-g1f07476ec143 and it gives a new W+X warning.
This still happens in 4.15 and 4.16-rc2+.
What can I do to help resolving it?
> [ 10.880663] ------------[ cut here ]------------
> [ 10.880755] x86/mm: Found insecure W+X mapping at address 00000000d051fb08/0xffff880000000000
> [ 10.880900] WARNING: CPU: 2 PID: 1 at arch/x86/mm/dump_pagetables.c:266 note_page+0x718/0xb89
> [ 10.881035] Modules linked in:
> [ 10.881128] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 4.15.0-rc9-00023-g1f07476ec143 #104
> [ 10.881264] Hardware name: Intel /SE7520JR22S, BIOS SE7520JR22.86B.P.10.00.0087.120820051348 12/08/2005
> [ 10.881405] RIP: 0010:note_page+0x718/0xb89
> [ 10.881491] RSP: 0000:ffffc90000013e48 EFLAGS: 00010296
> [ 10.881578] RAX: 0000000000000051 RBX: ffffc90000013ec8 RCX: ffffffff8164f938
> [ 10.881666] RDX: 0000000000000001 RSI: 0000000000000092 RDI: ffffffff82b468cc
> [ 10.881756] RBP: 0000000000000061 R08: 0000000000000177 R09: 00000000000001d7
> [ 10.881844] R10: 0720072007200720 R11: 0720072007200720 R12: 0000000000000000
> [ 10.881932] R13: 0000000000000000 R14: 0000000000000001 R15: 8800000990000000
> [ 10.882022] FS: 0000000000000000(0000) GS:ffff88003fc80000(0000) knlGS:0000000000000000
> [ 10.882156] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [ 10.882243] CR2: 0000000000000000 CR3: 000000000200a000 CR4: 00000000000006e0
> [ 10.882331] Call Trace:
> [ 10.882423] ptdump_walk_pgd_level_core+0x367/0x3a5
> [ 10.882511] ptdump_walk_pgd_level_checkwx+0x10/0x3e
> [ 10.882602] kernel_init+0x2e/0x10f
> [ 10.882688] ? rest_init+0xb9/0xb9
> [ 10.882775] ret_from_fork+0x35/0x40
> [ 10.882861] Code: fb ff ff 41 f7 c7 00 10 00 00 0f 85 e2 fe ff ff e9 36 fd ff ff c6 05 7d 45 6f 01 01 48 89 f2 48 c7 c7 08 5b ee 81 e8 4b d6 00 00 <0f> ff 48 8b 73 10 e9 bc f9 ff ff 4d 85 ed 0f 84 b9 01 00 00 41
> [ 10.883103] ---[ end trace bc3e2cf1a1adfa39 ]---
> [ 10.896336] x86/mm: Checked W+X mappings: FAILED, 266243 W+X pages found.
> [ 10.896430] x86/mm: Checking user space page tables
> [ 10.909522] x86/mm: Checked W+X mappings: FAILED, 56 W+X pages found.
--
Meelis Roos (mroos@linux.ee)
next prev parent reply other threads:[~2018-02-26 9:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-24 19:30 4.15-rc9 new insecure W+X mapping warning Meelis Roos
2018-02-26 9:29 ` Meelis Roos [this message]
2018-03-22 9:48 ` Meelis Roos
2018-03-09 18:54 ` Meelis Roos
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=alpine.LRH.2.21.1802261127370.4893@math.ut.ee \
--to=mroos@linux.ee \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).