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:
ABRT does not respect ulimit values.
Coredump is generated even if core is set to 0
Version-Release number of selected component (if applicable):
abrt-2.1.11-50.el7.x86_64
How reproducible:
Always
Steps to Reproduce:
1.ulimit -c 0
2. cat /proc/sys/kernel/core_pattern
|/usr/libexec/abrt-hook-ccpp %s %c %p %u %g %t e %P %I %h
3. sleep 1000&
4. kill -11 $!
Actual results:
Crash report generated in /var/spool/abrt
Expected results:
No crash report (or ulimit value respected)
Additional info:
If this is expected behavior what is role of %c here?
On FC 29 no crash report generated if limit is 0
This was always this way. And it was always documented this way. I understand, that it would be nice to parse %c, but this would be a feature. With RHEL7 currently being already in Maintainance 1 phase, this will not get into RHEL 7.
In RHEL 8, this hook is not used as ABRT reads code dumps from coredumpctl - so it does not have the sense to work on this in upstream as well.
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, 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:1025