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>
This commit is contained in:
parent
47ef4ad268
commit
89e6ffd9f0
@ -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__ */
|
||||
|
@ -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)
|
||||
|
Loading…
Reference in New Issue
Block a user