diff options
| author |   Eric W. Biederman <ebiederm@xmission.com> | 2018-04-16 13:55:53 -0500 |
|---|---|---|
| committer | Eric W. Biederman <ebiederm@xmission.com> | 2018-09-27 21:58:04 +0200 |
| commit | b92adb74adde62d9a9780ff2977d63dcb21aeaa6 (patch) | |
| tree | c7eee18a7b093092223997b45368d334a80c42f6 /arch/ia64/kernel/unaligned.c | |
| parent | signal/ia64: Use the generic force_sigsegv in setup_frame (diff) | |
| download | linux-dev-b92adb74adde62d9a9780ff2977d63dcb21aeaa6.tar.xz linux-dev-b92adb74adde62d9a9780ff2977d63dcb21aeaa6.zip | |
signal/ia64: Use the force_sig(SIGSEGV,...) in ia64_rt_sigreturn
The ia64 handling of failure to return from a signal frame has been trying
to set overlapping fields in struct siginfo since 2.3.43. The si_code
corresponds to the fields that were stomped (not the field that is
actually written), so I can not imagine a piece of userspace code
making sense of the signal frame if it looks closely.
In practice failure to return from a signal frame is a rare event that
almost never happens. Someone using an alternate signal stack to
recover and looking in detail is even more rare. So I presume no one
has ever noticed and reported this ia64 nonsense.
Sort this out by causing ia64 to use force_sig(SIGSEGV) like other architectures.
Fixes: 2.3.43
Cc: Tony Luck <tony.luck@intel.com>
Cc: Fenghua Yu <fenghua.yu@intel.com>
Cc: linux-ia64@vger.kernel.org
Acked-by: Tony Luck <tony.luck@intel.com>
Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions