| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 24 Jul 2014 00:18:15 +0300 From: Stefan Kristiansson <stefan.kristiansson@...nalahti.fi> To: linux-kernel@...r.kernel.org, linux@...ts.openrisc.net Cc: jonas@...thpole.se, Stefan Kristiansson <stefan.kristiansson@...nalahti.fi> Subject: [PATCH 5/6] openrisc: include l.swa in check for write data pagefault The way to determine if a data pagefault was caused by a write is to read the instruction at the PC that caused the fault and check if it's a store instruction. To recognize pagefaults caused by the l.swa instruction with opcode 0x33, has to be included in the check. Signed-off-by: Stefan Kristiansson <stefan.kristiansson@...nalahti.fi> --- arch/openrisc/kernel/entry.S | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/openrisc/kernel/entry.S b/arch/openrisc/kernel/entry.S index 572d223..aac0bde 100644 --- a/arch/openrisc/kernel/entry.S +++ b/arch/openrisc/kernel/entry.S @@ -264,7 +264,7 @@ EXCEPTION_ENTRY(_data_page_fault_handler) l.srli r6,r6,26 // check opcode for write access #endif - l.sfgeui r6,0x34 // check opcode for write access + l.sfgeui r6,0x33 // check opcode for write access l.bnf 1f l.sfleui r6,0x37 l.bnf 1f -- 1.8.3.2 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists