From: timur@codeaurora.org (Timur Tabi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: fix CONFIG_DEBUG_WX address reporting
Date: Thu, 14 Dec 2017 15:34:13 -0600 [thread overview]
Message-ID: <825594ef-4db5-ec71-9ad8-81f447993251@codeaurora.org> (raw)
In-Reply-To: <673df793-cc4c-b251-6846-7cba4931ff53@redhat.com>
On 12/14/2017 01:02 PM, Laura Abbott wrote:
>
> While we're fixing this up, do you want to drop the %p from the
> "Found insecure W+X" message from above since pointer hashing
> renders it kind of pointless or switch it to %px?
Switching to %px gives me:
arm64/mm: Found insecure W+X mapping at address
ffff2b1b4e512000/0xffff2b1b4e512000
Looks the same as before.
However, when I try to dump the contents of memory at that address via
print_hex_dump(), I get an "Unable to handle kernel paging request" oops.
[ 11.236091] Unable to handle kernel paging request at virtual address
ffff2b1b4e512000
[ 11.243985] pgd = ffff2b1b55a0d000
[ 11.247371] [ffff2b1b4e512000] *pgd=00000007ffffe003,
*pud=00000007ffffd003, *pmd=000000079972a003, *pte=0000000000000000
--
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm
Technologies, Inc. Qualcomm Technologies, Inc. is a member of the
Code Aurora Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2017-12-14 21:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 22:57 How to debug "insecure W+X mapping"? Timur Tabi
2017-12-12 23:30 ` Laura Abbott
2017-12-13 11:58 ` [PATCH] arm64: fix CONFIG_DEBUG_WX address reporting (was: Re: How to debug "insecure W+X mapping"?) Mark Rutland
2017-12-14 19:02 ` [PATCH] arm64: fix CONFIG_DEBUG_WX address reporting Laura Abbott
2017-12-14 21:34 ` Timur Tabi [this message]
2017-12-14 19:03 ` Timur Tabi
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=825594ef-4db5-ec71-9ad8-81f447993251@codeaurora.org \
--to=timur@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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