aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKristina Martsenko <kristina.martsenko@arm.com>2017-06-09 16:35:53 +0100
committerWill Deacon <will.deacon@arm.com>2017-06-12 12:33:37 +0100
commitbf396c09c2447a787d02af34cf167e953f85fa42 (patch)
treec921b42eb6803d2d11e06af6cb3832d443f5f102
parentarm64: mm: print out correct page table entries (diff)
downloadlinux-dev-bf396c09c2447a787d02af34cf167e953f85fa42.tar.xz
linux-dev-bf396c09c2447a787d02af34cf167e953f85fa42.zip
arm64: mm: don't print out page table entries on EL0 faults
When we take a fault from EL0 that can't be handled, we print out the page table entries associated with the faulting address. This allows userspace to print out any current page table entries, including kernel (TTBR1) entries. Exposing kernel mappings like this could pose a security risk, so don't print out page table information on EL0 faults. (But still print it out for EL1 faults.) This also follows the same behaviour as x86, printing out page table entries on kernel mode faults but not user mode faults. Acked-by: Mark Rutland <mark.rutland@arm.com> Signed-off-by: Kristina Martsenko <kristina.martsenko@arm.com> Signed-off-by: Will Deacon <will.deacon@arm.com>
-rw-r--r--arch/arm64/mm/fault.c1
1 files changed, 0 insertions, 1 deletions
diff --git a/arch/arm64/mm/fault.c b/arch/arm64/mm/fault.c
index 9d27b1720c52..b5a1605398b7 100644
--- a/arch/arm64/mm/fault.c
+++ b/arch/arm64/mm/fault.c
@@ -264,7 +264,6 @@ static void __do_user_fault(struct task_struct *tsk, unsigned long addr,
pr_info("%s[%d]: unhandled %s (%d) at 0x%08lx, esr 0x%03x\n",
tsk->comm, task_pid_nr(tsk), inf->name, sig,
addr, esr);
- show_pte(addr);
__show_regs(regs);
}