Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
The current text is shown below:
In most cases where execve() fails, control returns to the original executable image, and the caller of
execve() can then handle the error. However, in (rare) cases (typically caused by resource exhaustion),
failure may occur past the point of no return: the original executable image has been torn down, but the new
image could not be completely built. In such cases, the kernel kills the process with a SIGKILL signal.
This is not true anymore, process is killed with SIGSEGV signal, not SIGKILL since integration of the following commit:
https://github.com/torvalds/linux/commit/19d860a140beac48a1377f179e693abe86a9dac9
Version-Release number of selected component (if applicable):
All versions
Additional info:
See also BZ #1828825
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (man-pages-overrides bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2020:4675
Description of problem: The current text is shown below: In most cases where execve() fails, control returns to the original executable image, and the caller of execve() can then handle the error. However, in (rare) cases (typically caused by resource exhaustion), failure may occur past the point of no return: the original executable image has been torn down, but the new image could not be completely built. In such cases, the kernel kills the process with a SIGKILL signal. This is not true anymore, process is killed with SIGSEGV signal, not SIGKILL since integration of the following commit: https://github.com/torvalds/linux/commit/19d860a140beac48a1377f179e693abe86a9dac9 Version-Release number of selected component (if applicable): All versions Additional info: See also BZ #1828825