From: Joerg Roedel <jroedel@suse.de>
To: kernel test robot <lkp@intel.com>
Cc: LKP <lkp@01.org>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: a13c600e15 ("x86/mm/pti: Move user W+X check into .."): WARNING: CPU: 0 PID: 1 at arch/x86/mm/dump_pagetables.c:283 note_page
Date: Fri, 10 Aug 2018 09:30:16 +0200 [thread overview]
Message-ID: <20180810073016.fn7wrkkdm5p7zv53@suse.de> (raw)
In-Reply-To: <5b6cc146.lVmfvLKHKgZxC5d8%lkp@intel.com>
On Fri, Aug 10, 2018 at 06:33:42AM +0800, kernel test robot wrote:
> [ 9.635329] x86/mm: Checking user space page tables
> [ 9.636271] ------------[ cut here ]------------
> [ 9.637045] x86/mm: Found insecure W+X mapping at address (ptrval)/0xffc01000
> [ 9.638228] WARNING: CPU: 0 PID: 1 at arch/x86/mm/dump_pagetables.c:283 note_page+0x66b/0x870
Hmm, weird, this warning triggers for 32-bit non-pae. There is no
NX-bit in this mode, so the check shouldn't happen there. I'll
investigate.
Joerg
next prev parent reply other threads:[~2018-08-10 7:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-09 22:33 a13c600e15 ("x86/mm/pti: Move user W+X check into .."): WARNING: CPU: 0 PID: 1 at arch/x86/mm/dump_pagetables.c:283 note_page kernel test robot
2018-08-10 7:30 ` Joerg Roedel [this message]
2018-08-10 8:35 ` Joerg Roedel
2018-08-16 3:08 ` [LKP] " Rong Chen
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=20180810073016.fn7wrkkdm5p7zv53@suse.de \
--to=jroedel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=lkp@intel.com \
--cc=tglx@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;
as well as URLs for NNTP newsgroup(s).