Files
linux/arch/sparc/kernel
Eric W. Biederman cc9f72e474 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>
2017-07-19 19:13:14 -05:00
..
2014-05-18 19:01:30 -07:00
2014-05-18 19:01:29 -07:00
2017-06-01 09:42:46 -07:00
2016-08-07 23:55:43 -04:00
2017-03-28 18:24:00 -04:00
2016-08-07 23:55:43 -04:00
2016-11-18 11:16:59 -08:00
2016-08-07 23:55:43 -04:00
2016-07-27 22:53:17 -07:00
2017-06-06 16:41:47 -04:00
2017-06-12 15:44:03 -07:00
2015-03-19 10:17:22 -05:00
2016-12-11 18:01:51 -08:00
2017-03-27 21:51:40 -07:00
2015-03-19 18:54:49 -07:00
2017-06-25 22:01:11 -04:00
2013-06-13 22:12:14 +01:00
2012-03-28 18:30:03 +01:00
2017-03-27 21:51:40 -07:00
2017-06-12 15:44:03 -07:00
2017-06-06 13:45:29 -07:00
2017-03-27 21:51:40 -07:00
2014-07-21 22:27:56 -07:00
2017-04-23 18:28:55 -07:00
2017-04-23 18:28:55 -07:00
2017-06-15 08:25:19 -07:00
2017-06-25 22:01:11 -04:00
2017-06-06 13:45:29 -07:00
2017-03-27 21:51:40 -07:00
2017-03-27 21:51:40 -07:00