From: jlinton@redhat.com (Jeremy Linton)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] [PATCH] arm64: Boot failure on m400 with new cont PTEs
Date: Mon, 23 Nov 2015 12:46:05 -0600 [thread overview]
Message-ID: <56535EED.5040401@redhat.com> (raw)
In-Reply-To: <5653524B.40302@labbott.name>
On 11/23/2015 11:52 AM, Laura Abbott wrote:
> On 11/23/15 8:42 AM, Jeremy Linton wrote:
>> On 11/23/2015 10:37 AM, Laura Abbott wrote:
>>> Which permissions still need to be cleaned up from your perspective?
>>
>> IMHO, the vast majority of the linear map should not be
>> executable/read/write, which is what happens today.
>>
>
> With CONFIG_DEBUG_RODATA on I'm not seeing any rwx regions
> 0xffffffc000000000-0xffffffc000080000 512K RW NX SHD AF
> CON UXN MEM/NORMAL
> 0xffffffc000080000-0xffffffc000082000 8K RW NX SHD
> AF UXN MEM/NORMAL
> 0xffffffc000082000-0xffffffc000090000 56K ro x SHD
> AF UXN MEM/NORMAL
> 0xffffffc000090000-0xffffffc000200000 1472K ro x SHD AF
> CON UXN MEM/NORMAL
> 0xffffffc000200000-0xffffffc000800000 6M ro x SHD
> AF BLK UXN MEM/NORMAL
> 0xffffffc000800000-0xffffffc000980000 1536K ro x SHD AF
> CON UXN MEM/NORMAL
> 0xffffffc000980000-0xffffffc000987000 28K ro x SHD
> AF UXN MEM/NORMAL
> 0xffffffc000987000-0xffffffc000990000 36K RW NX SHD
> AF UXN MEM/NORMAL
> 0xffffffc000990000-0xffffffc000a00000 448K RW NX SHD AF
> CON UXN MEM/NORMAL
> 0xffffffc000a00000-0xffffffc000a10000 64K RW NX SHD
> AF UXN MEM/NORMAL
> 0xffffffc000a10000-0xffffffc000c00000 1984K RW NX SHD AF
> CON UXN MEM/NORMAL
> 0xffffffc000c00000-0xffffffc040000000 1012M RW NX SHD
> AF BLK UXN MEM/NORMAL
> 0xffffffc040000000-0xffffffc080000000 1G RW NX SHD
> AF BLK UXN MEM/NORMAL
>
> are there other parts of the map you're seeing that aren't on my system?
Thats my mistake, I didn't remember seeing the NX set for the block
mappings with the RO case, the machine I just checked looks good too.
So, I you can ignore that little rant.
next prev parent reply other threads:[~2015-11-23 18:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 15:03 [PATCH] [PATCH] arm64: Boot failure on m400 with new cont PTEs Jeremy Linton
2015-11-18 15:20 ` Mark Rutland
2015-11-18 16:08 ` Jeremy Linton
2015-11-18 16:29 ` Mark Rutland
2015-11-18 17:14 ` Jeremy Linton
2015-11-18 18:04 ` Mark Rutland
2015-11-18 19:31 ` Jeremy Linton
2015-11-19 11:31 ` Mark Rutland
2015-11-20 19:52 ` Mark Rutland
2015-11-23 12:15 ` Catalin Marinas
2015-11-23 13:49 ` Mark Rutland
2015-11-23 14:48 ` Jeremy Linton
2015-11-23 15:41 ` Will Deacon
2015-11-23 15:46 ` Jeremy Linton
2015-11-23 14:31 ` Jeremy Linton
2015-11-20 20:15 ` Mark Rutland
2015-11-23 15:51 ` Catalin Marinas
2015-11-23 16:02 ` Jeremy Linton
2015-11-23 16:37 ` Laura Abbott
2015-11-23 16:42 ` Jeremy Linton
2015-11-23 17:52 ` Laura Abbott
2015-11-23 18:46 ` Jeremy Linton [this message]
2015-11-24 8:04 ` Ard Biesheuvel
2015-11-23 16:52 ` Catalin Marinas
2015-11-23 17:24 ` Catalin Marinas
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=56535EED.5040401@redhat.com \
--to=jlinton@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.