[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20160929213257.30505-1-labbott@redhat.com>
Date: Thu, 29 Sep 2016 14:32:54 -0700
From: Laura Abbott <labbott@...hat.com>
To: AKASHI Takahiro <takahiro.akashi@...aro.org>,
Mark Rutland <mark.rutland@....com>,
Ard Biesheuvel <ard.biesheuvel@...aro.org>,
David Brown <david.brown@...aro.org>,
Will Deacon <will.deacon@....com>,
Catalin Marinas <catalin.marinas@....com>
Cc: Laura Abbott <labbott@...hat.com>,
linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org,
Kees Cook <keescook@...omium.org>,
kernel-hardening@...ts.openwall.com
Subject: [PATCH 0/3] WX Checking for arm64
Hi,
This is an implementation to check for writable and executable pages on arm64.
This is heavily based on the x86 version which uses the existing page table
dumping code to do the checking. Some notes:
- The W^X checking is important so this option should become defaut eventually.
To make this feasible, the debugfs functionality has been split out as a
separate option. I didn't see a good way to make it modular like x86 but
an option should be good enough.
- This checks all page tables registered with ptdump_register. I don't see this
being called elsewhere right now though.
- Once this is merged, I'd like to see about moving DEBUG_WX to the top level
instead of having each arch call it in mark_rodata.
Laura Abbott (3):
arm64: dump: Make ptdump debugfs a separate option
arm64: dump: Make the page table dumping seq_file optional
arm64: dump: Add checking for writable and exectuable pages
arch/arm64/Kconfig.debug | 34 ++++++++++++++-
arch/arm64/include/asm/ptdump.h | 25 ++++++++++-
arch/arm64/mm/Makefile | 3 +-
arch/arm64/mm/dump.c | 92 ++++++++++++++++++++++++++++-------------
arch/arm64/mm/mmu.c | 2 +
arch/arm64/mm/ptdump_debugfs.c | 33 +++++++++++++++
6 files changed, 157 insertions(+), 32 deletions(-)
create mode 100644 arch/arm64/mm/ptdump_debugfs.c
--
2.10.0
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
