summaryrefslogtreecommitdiff
path: root/arch/m68k/include/asm/processor.h
diff options
context:
space:
mode:
authorGreg Ungerer <gerg@linux-m68k.org>2016-07-21 09:28:48 +0300
committerGreg Ungerer <gerg@linux-m68k.org>2016-07-25 07:40:28 +0300
commit89e6ffd9f03936d9f6f0332426e4a3cf379b90bd (patch)
tree0a889cd15af53bece41ba4997111809fa3f4be73 /arch/m68k/include/asm/processor.h
parent47ef4ad2684d380dd6d596140fb79395115c3950 (diff)
downloadlinux-89e6ffd9f03936d9f6f0332426e4a3cf379b90bd.tar.xz
m68k: fix bFLT executable running on MMU enabled systems
Even after recent changes to support running flat format executables on MMU enabled systems (by nicolas.pitre@linaro.org) they still failed to run on m68k/ColdFire MMU enabled systems. On trying to run a flat format binary the application would immediately crash with a SIGSEGV. Code to setup the D5 register with the base of the application data region was only in the non-MMU code path, so it was not being set for the MMU enabled case. Flat binaries on m68k/ColdFire use this to support GOT/PIC flat built application code. Fix this so that D5 is always setup when loading/running a bFLT executable on m68k systems. Signed-off-by: Greg Ungerer <gerg@linux-m68k.org>
Diffstat (limited to 'arch/m68k/include/asm/processor.h')
-rw-r--r--arch/m68k/include/asm/processor.h2
1 files changed, 0 insertions, 2 deletions
diff --git a/arch/m68k/include/asm/processor.h b/arch/m68k/include/asm/processor.h
index a6ce2ec8d693..46672d1f4d62 100644
--- a/arch/m68k/include/asm/processor.h
+++ b/arch/m68k/include/asm/processor.h
@@ -131,8 +131,6 @@ extern int handle_kernel_fault(struct pt_regs *regs);
do { \
(_regs)->pc = (_pc); \
setframeformat(_regs); \
- if (current->mm) \
- (_regs)->d5 = current->mm->start_data; \
(_regs)->sr &= ~0x2000; \
wrusp(_usp); \
} while(0)