diff options
| author | Eric W. Biederman <ebiederm@xmission.com> | 2017-07-17 03:04:58 +0200 |
|---|---|---|
| committer | Eric W. Biederman <ebiederm@xmission.com> | 2017-07-20 02:13:14 +0200 |
| commit | cc9f72e474a4da365896d0e528da324f205e8b31 (patch) | |
| tree | cda3b38a86ae57b171c6094a6ef405b17ac75260 /kernel/sched | |
| parent | signal/ia64: Document a conflict with SI_USER with SIGFPE (diff) | |
| download | linux-cc9f72e474a4da365896d0e528da324f205e8b31.tar.xz 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 'kernel/sched')
0 files changed, 0 insertions, 0 deletions