Bug 154972 - unexplained SIGSEGV death in SIGSEGV signal handler
unexplained SIGSEGV death in SIGSEGV signal handler
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel (Show other bugs)
i686 Linux
high Severity high
: ---
: ---
Assigned To: Roland McGrath
Brian Brock
Depends On: 154221
  Show dependency treegraph
Reported: 2005-04-15 03:23 EDT by Roland McGrath
Modified: 2007-11-30 17:07 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-06-08 11:14:09 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
reproducer, compile on 2.1AS and run on RHEL4 (31.85 KB, application/octet-stream)
2005-04-15 03:23 EDT, Roland McGrath
no flags Details

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2005:420 normal SHIPPED_LIVE Important: Updated kernel packages available for Red Hat Enterprise Linux 4 Update 1 2005-06-08 00:00:00 EDT

  None (edit)
Description Roland McGrath 2005-04-15 03:23:05 EDT
Split off from Bug #154221

With bug #154221 fixed, we can get a core dump for this case.
Why it happens remains unclear.
Comment 1 Roland McGrath 2005-04-15 03:23:06 EDT
Created attachment 113213 [details]
reproducer, compile on 2.1AS and run on RHEL4
Comment 2 Roland McGrath 2005-04-23 21:02:20 EDT
The problem here turns out to be an interaction between bug #154221 and the
exec-shield implementation on x86.  Fixing that bug in a way that interacts well
with the exec-shield code alleviates the spurious faults.
See bug #154221 comment #23 for a patch that addresses this problem.  
This patch is still under review by the RHEL4 kernel team and not verified to be
without other consequences.

The chances of hitting this problem should be drastically reduced by booting
with the exec-shield=0 parameter.  Using the test case here, I have not been
able to reproduce the problem when exec-shield=0 is set at boot time.  However,
I cannot be sure that the problem could never arise in that configuration.
Comment 6 Tim Powers 2005-06-08 11:14:09 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.