summaryrefslogtreecommitdiffstats
path: root/arch/sparc/kernel/traps_32.c
diff options
context:
space:
mode:
authorEric W. Biederman <ebiederm@xmission.com>2017-07-16 20:04:58 -0500
committerEric W. Biederman <ebiederm@xmission.com>2017-07-19 19:13:14 -0500
commitcc9f72e474a4da365896d0e528da324f205e8b31 (patch)
treecda3b38a86ae57b171c6094a6ef405b17ac75260 /arch/sparc/kernel/traps_32.c
parent80dce5e37493029e1fb7f890b960264ba9a46fe4 (diff)
downloadlinux-cc9f72e474a4da365896d0e528da324f205e8b31.tar.gz
linux-cc9f72e474a4da365896d0e528da324f205e8b31.tar.bz2
linux-cc9f72e474a4da365896d0e528da324f205e8b31.zip
signal/sparc: Document a conflict with SI_USER with SIGFPE
Setting si_code to __SI_FAULT results in a userspace seeing an si_code of 0. This is the same si_code as SI_USER. Posix and common sense requires that SI_USER not be a signal specific si_code. As such this use of 0 for the si_code is a pretty horribly broken ABI. This was introduced in 2.3.41 so this mess has had a long time for people to be able to start depending on it. As this bug has existed for 17 years already I don't know if it is worth fixing. It is definitely worth documenting what is going on so that no one decides to copy this bad decision. Cc: "David S. Miller" <davem@davemloft.net> Cc: sparclinux@vger.kernel.org Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>
Diffstat (limited to 'arch/sparc/kernel/traps_32.c')
-rw-r--r--arch/sparc/kernel/traps_32.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/sparc/kernel/traps_32.c b/arch/sparc/kernel/traps_32.c
index 466d4aed06c7..581cf35ee7e3 100644
--- a/arch/sparc/kernel/traps_32.c
+++ b/arch/sparc/kernel/traps_32.c
@@ -306,7 +306,7 @@ void do_fpe_trap(struct pt_regs *regs, unsigned long pc, unsigned long npc,
info.si_errno = 0;
info.si_addr = (void __user *)pc;
info.si_trapno = 0;
- info.si_code = __SI_FAULT;
+ info.si_code = FPE_FIXME;
if ((fsr & 0x1c000) == (1 << 14)) {
if (fsr & 0x10)
info.si_code = FPE_FLTINV;