[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20170328213431.10904-3-opendmb@gmail.com>
Date: Tue, 28 Mar 2017 14:34:25 -0700
From: Doug Berger <opendmb@...il.com>
To: mark.rutland@....com
Cc: robh+dt@...nel.org, catalin.marinas@....com, will.deacon@....com,
computersforpeace@...il.com, gregory.0xf0@...il.com,
f.fainelli@...il.com, bcm-kernel-feedback-list@...adcom.com,
opendmb@...il.com, wangkefeng.wang@...wei.com, james.morse@....com,
mingo@...nel.org, sandeepa.s.prabhu@...il.com,
shijie.huang@....com, linus.walleij@...aro.org, treding@...dia.com,
jonathanh@...dia.com, olof@...om.net, mirza.krak@...il.com,
suzuki.poulose@....com, bgolaszewski@...libre.com,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org
Subject: [PATCH v2 2/8] arm64: mm: mark fault_info __ro_after_init
The fault_info table must be made writeable to allow installation
of custom memory abort handlers, but it can be made read-only
after initialization to provide some protection.
Signed-off-by: Doug Berger <opendmb@...il.com>
---
arch/arm64/mm/fault.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/mm/fault.c b/arch/arm64/mm/fault.c
index cdf1260f1005..43319ed58a47 100644
--- a/arch/arm64/mm/fault.c
+++ b/arch/arm64/mm/fault.c
@@ -493,7 +493,7 @@ static struct fault_info {
int sig;
int code;
const char *name;
-} fault_info[] = {
+} fault_info[] __ro_after_init = {
{ do_bad, SIGBUS, 0, "ttbr address size fault" },
{ do_bad, SIGBUS, 0, "level 1 address size fault" },
{ do_bad, SIGBUS, 0, "level 2 address size fault" },
--
2.12.0
Powered by blists - more mailing lists