From: Thomas Gleixner <tglx@linutronix.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: x86@linutronix.de, Kees Cook <keescook@chromium.org>
Subject: [WARNING] x86/mm: Found insecure W+X mapping at address ..
Date: Tue, 23 May 2017 17:40:39 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1705231734130.2740@nanos> (raw)
As of 4.12-rc1 one of my machines triggers the insecure W+X mapping.
It's consistenly 9 entries close to the beginning of the module space,
before the first actual module starts. See below.
Any ideas which avoid bisecting would be appreciated.
Thanks,
tglx
---[ Modules ]---
0xffffffffc0000000-0xffffffffc017d000 1524K pte
0xffffffffc017d000-0xffffffffc017e000 4K RW GLB x pte
0xffffffffc017e000-0xffffffffc017f000 4K pte
0xffffffffc017f000-0xffffffffc0180000 4K RW GLB x pte
0xffffffffc0180000-0xffffffffc0181000 4K pte
0xffffffffc0181000-0xffffffffc0182000 4K RW GLB x pte
0xffffffffc0182000-0xffffffffc0183000 4K pte
0xffffffffc0183000-0xffffffffc0184000 4K RW GLB x pte
0xffffffffc0184000-0xffffffffc0185000 4K pte
0xffffffffc0185000-0xffffffffc0186000 4K RW GLB x pte
0xffffffffc0186000-0xffffffffc0187000 4K pte
0xffffffffc0187000-0xffffffffc0188000 4K RW GLB x pte
0xffffffffc0188000-0xffffffffc0189000 4K pte
0xffffffffc0189000-0xffffffffc018a000 4K RW GLB x pte
0xffffffffc018a000-0xffffffffc018b000 4K pte
0xffffffffc018b000-0xffffffffc018c000 4K RW GLB x pte
0xffffffffc018c000-0xffffffffc018d000 4K pte
0xffffffffc018d000-0xffffffffc018e000 4K RW GLB x pte
First module starts here:
0xffffffffc018e000-0xffffffffc0191000 12K pte
0xffffffffc0191000-0xffffffffc0192000 4K ro GLB x pte
---[ Modules ]---
0xffffffffc0000000-0xffffffffc0200000 2M pmd
0xffffffffc0200000-0xffffffffc02f8000 992K pte
0xffffffffc02f8000-0xffffffffc02f9000 4K RW GLB x pte
0xffffffffc02f9000-0xffffffffc02fa000 4K pte
0xffffffffc02fa000-0xffffffffc02fb000 4K RW GLB x pte
0xffffffffc02fb000-0xffffffffc02fc000 4K pte
0xffffffffc02fc000-0xffffffffc02fd000 4K RW GLB x pte
0xffffffffc02fd000-0xffffffffc02fe000 4K pte
0xffffffffc02fe000-0xffffffffc02ff000 4K RW GLB x pte
0xffffffffc02ff000-0xffffffffc0300000 4K pte
0xffffffffc0300000-0xffffffffc0301000 4K RW GLB x pte
0xffffffffc0301000-0xffffffffc0302000 4K pte
0xffffffffc0302000-0xffffffffc0303000 4K RW GLB x pte
0xffffffffc0303000-0xffffffffc0304000 4K pte
0xffffffffc0304000-0xffffffffc0305000 4K RW GLB x pte
0xffffffffc0305000-0xffffffffc0306000 4K pte
0xffffffffc0306000-0xffffffffc0307000 4K RW GLB x pte
0xffffffffc0307000-0xffffffffc0308000 4K pte
0xffffffffc0308000-0xffffffffc0309000 4K RW GLB x pte
First module starts here:
0xffffffffc0309000-0xffffffffc030c000 12K pte
0xffffffffc030c000-0xffffffffc030d000 4K ro GLB x pte
next reply other threads:[~2017-05-23 15:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 15:40 Thomas Gleixner [this message]
2017-05-23 15:54 ` [WARNING] x86/mm: Found insecure W+X mapping at address Kees Cook
2017-05-23 16:35 ` Thomas Gleixner
2017-05-23 20:48 ` Thomas Gleixner
2017-05-23 22:59 ` Steven Rostedt
2017-05-24 6:20 ` Thomas Gleixner
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.DEB.2.20.1705231734130.2740@nanos \
--to=tglx@linutronix.de \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@linutronix.de \
/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