diff options
| author | Eric W. Biederman <ebiederm@xmission.com> | 2017-07-16 19:35:35 -0500 |
|---|---|---|
| committer | Eric W. Biederman <ebiederm@xmission.com> | 2017-07-19 19:13:14 -0500 |
| commit | 80dce5e37493029e1fb7f890b960264ba9a46fe4 (patch) | |
| tree | 620b18ab95c50f595e850f414fb0f0911cbd0364 /arch/sparc/kernel/traps_32.c | |
| parent | e2bd64d92a10f34b425cf3884c6032588c661335 (diff) | |
| download | linux-80dce5e37493029e1fb7f890b960264ba9a46fe4.tar.gz linux-80dce5e37493029e1fb7f890b960264ba9a46fe4.tar.bz2 linux-80dce5e37493029e1fb7f890b960264ba9a46fe4.zip | |
signal/ia64: 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.
Given that ia64 is on it's last legs I don't know that it is worth
fixing this, but it is worth documenting what is going on so that
no one decides to copy this bad decision.
This was introduced in 2.3.51 so this mess has had a long time for
people to be able to start depending on it.
Cc: Tony Luck <tony.luck@intel.com>
Cc: Fenghua Yu <fenghua.yu@intel.com>
Cc: linux-ia64@vger.kernel.org
Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>
Diffstat (limited to 'arch/sparc/kernel/traps_32.c')
0 files changed, 0 insertions, 0 deletions