summaryrefslogtreecommitdiff
path: root/arch
diff options
context:
space:
mode:
authorT.J. Purtell <tj@mobisocial.us>2013-11-05 16:52:10 +0900
committerChanho Park <chanho61.park@samsung.com>2014-11-18 11:45:23 +0900
commit8d9a7d6f86211b04b7ef524812d0213d61534c83 (patch)
tree60a877a6e6585e24c2ad38b7cfa02940157df627 /arch
parent044b2717eb74cc940c896c6899c7827cdfbbd477 (diff)
downloadlinux-3.10-8d9a7d6f86211b04b7ef524812d0213d61534c83.tar.gz
linux-3.10-8d9a7d6f86211b04b7ef524812d0213d61534c83.tar.bz2
linux-3.10-8d9a7d6f86211b04b7ef524812d0213d61534c83.zip
arm: Thumb=>ARM signal handling setup skips the a few instructions on Snapdragon S4/Krait
The Thumb instruction set include an If-Then instruction. If an ARM function is registered as a signal handler, and that signal is delivered inside the block of instructions follow the IT instruction, some of the instructions at the beginning of the signal handler are skipped. This occurs because the IT state bits of the Program Status Register are not cleared by the kernel. The ARM architecture reference specifies that the IT state bits in the PSR must be all zeros in ARM mode or behavior is unspecified. On the Qualcomm Snapdragon S4/Krait architecture CPUs the processor continues to consider the IT state bits while in ARM mode. This makes it so that some instructions are skipped by the CPU. The relevant clipping of the ARM architecture document is available here: https://www.dropbox.com/s/6hpwey3kklw20c1/ITState-ARM-Architecture.pdf This manifests itself in code that uses a lot of signal handling concurrently with complicated logic code compiled for thumb when the signal handler compiled as ARM code. One example is the mono runtime. It uses a signal based mechanism to perform stop the world operation needed by its garbage collector. It is compiled for ARM and generates ARM code, however, bionic (libc for android) is compiled for thumb. During a test case involving native allocation in parallel with garbage collection (signal handling), we found that the test case would crash only when running on a Krait architecture CPU. We found the preceding instructions before the signal to always point to something inside an IT sequence, in this case the logic in the dlfree merging of free heap blocks. After adding a sequence of NOPs to the beginning of the signal handlers, the problem disappeared. We applied the attached patch to the kernel on one of the Krait devices and found that it also alleviated the crashes. The patch simply clears the IT State bits regardless of if the signal handler is an ARM/Thumb function. It also includes the same fix applied to the arm64 compat handler. Signed-off-by: T.J. Purtell <tj@mobisocial.us>
Diffstat (limited to 'arch')
-rw-r--r--arch/arm/kernel/signal.c12
1 files changed, 8 insertions, 4 deletions
diff --git a/arch/arm/kernel/signal.c b/arch/arm/kernel/signal.c
index 5a42c12767a..b1fb338fa73 100644
--- a/arch/arm/kernel/signal.c
+++ b/arch/arm/kernel/signal.c
@@ -375,12 +375,16 @@ setup_return(struct pt_regs *regs, struct ksignal *ksig,
*/
thumb = handler & 1;
- if (thumb) {
- cpsr |= PSR_T_BIT;
#if __LINUX_ARM_ARCH__ >= 7
- /* clear the If-Then Thumb-2 execution state */
- cpsr &= ~PSR_IT_MASK;
+ /*
+ * Clear the If-Then Thumb-2 execution state
+ * ARM spec requires this to be all 000s in ARM mode
+ */
+ cpsr &= ~PSR_IT_MASK;
#endif
+
+ if (thumb) {
+ cpsr |= PSR_T_BIT;
} else
cpsr &= ~PSR_T_BIT;
}