From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753187AbbJMVb1 (ORCPT ); Tue, 13 Oct 2015 17:31:27 -0400 Received: from mail-pa0-f47.google.com ([209.85.220.47]:32837 "EHLO mail-pa0-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752798AbbJMVbZ (ORCPT ); Tue, 13 Oct 2015 17:31:25 -0400 From: Mark Salyzyn To: linux-kernel@vger.kernel.org Cc: Mark Salyzyn , Catalin Marinas , Will Deacon , Mark Rutland , Marc Zyngier , AKASHI Takahiro , Daniel Thompson , linux-arm-kernel@lists.infradead.org Subject: Aarch32 user space PC alignment exception Date: Tue, 13 Oct 2015 14:30:51 -0700 Message-Id: <1444771874-22714-1-git-send-email-salyzyn@android.com> X-Mailer: git-send-email 2.6.0.rc2.230.g3dd15c0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org armv7 does not have a PC alignment exception. armv8 Aarch32 user space however can produce a PC alignment exception. Add handler so the we do not dump an unexpected stack trace in the logs. Signed-off-by: Mark Salyzyn --- arch/arm64/kernel/entry.S | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm64/kernel/entry.S b/arch/arm64/kernel/entry.S index 4306c93..7ed3d75 100644 --- a/arch/arm64/kernel/entry.S +++ b/arch/arm64/kernel/entry.S @@ -430,6 +430,8 @@ el0_sync_compat: b.eq el0_fpsimd_acc cmp x24, #ESR_ELx_EC_FP_EXC32 // FP/ASIMD exception b.eq el0_fpsimd_exc + cmp x24, #ESR_ELx_EC_PC_ALIGN // pc alignment exception + b.eq el0_sp_pc cmp x24, #ESR_ELx_EC_UNKNOWN // unknown exception in EL0 b.eq el0_undef cmp x24, #ESR_ELx_EC_CP15_32 // CP15 MRC/MCR trap -- 2.6.0.rc2.230.g3dd15c0