m68k: fix bFLT executable running on MMU enabled systems
authorGreg Ungerer <gerg@linux-m68k.org>
Thu, 21 Jul 2016 06:28:48 +0000 (16:28 +1000)
committerGreg Ungerer <gerg@linux-m68k.org>
Mon, 25 Jul 2016 04:40:28 +0000 (14:40 +1000)
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>
arch/m68k/include/asm/flat.h
arch/m68k/include/asm/processor.h

index f9454b89a51b9c763c6538688b1de1cc6fc01736..f46c2f044f8cb5d503834cd26bb59a22b6d9e3b7 100644 (file)
@@ -18,4 +18,10 @@ static inline int flat_set_persistent(unsigned long relval,
        return 0;
 }
 
+#define FLAT_PLAT_INIT(regs) \
+       do { \
+               if (current->mm) \
+                       (regs)->d5 = current->mm->start_data; \
+       } while (0)
+
 #endif /* __M68KNOMMU_FLAT_H__ */
index a6ce2ec8d693f1643c93fefc70d9934954b6a716..46672d1f4d620ccd8a96302503eee2239d85dd58 100644 (file)
@@ -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)