Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 13:03:42 -0600	[thread overview]
Message-ID: <53e20df7-9b41-31ec-21fe-30786ae7a0a6@codeaurora.org> (raw)
In-Reply-To: <20171213115835.pkt3fyqcbk7lgdeb@lakrids.cambridge.arm.com>

On 12/13/2017 05:58 AM, Mark Rutland wrote:
> Whoops; I think we forgot to apply the VA_START offset in
> ptdump_check_wx(), so we report the address wrong.
> 
> Does the below (untested) patch result in a sane-looking report?

[   10.977304] arm64/mm: Found insecure W+X mapping at address 
ffff190621232000/0xffff190621232000

I can reproduce the problem after 2-3 reboots.  When it happens, I get a 
different pair of addresses, but they all look like these.

I'm not sure what to do next, however.

-- 
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.

      parent reply	other threads:[~2017-12-14 19:03 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
2017-12-14 19:03     ` Timur Tabi [this message]

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=53e20df7-9b41-31ec-21fe-30786ae7a0a6@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