Bug 614486

Summary: kernel.core_pattern in /etc/sysctl.conf not getting set at boot
Product: Red Hat Enterprise Linux 6 Reporter: Casey Dahlin <cdahlin>
Component: abrtAssignee: Denys Vlasenko <dvlasenk>
Status: CLOSED ERRATA QA Contact: BaseOS QE - Apps <qe-baseos-apps>
Severity: medium Docs Contact:
Priority: low    
Version: 6.0CC: ahecox, dfeng, dvlasenk, gavin, jmoskovc, jwest, kklic, mnowak, notting, npajkovs, rvokal, spurrier, vanhoof
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: abrt-1.1.15-1.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-19 13:41:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 618602    
Bug Blocks: 627601    
Attachments:
Description Flags
Proposed patch
none
Updated patch (this one went to git) none

Description Casey Dahlin 2010-07-14 15:11:38 UTC
The value in /etc/sysctl.conf for kernel.core_pattern is not being set in the system /proc filesystem on boot. If you manually run sysctl -p it does get set. In addition, there are errors messages being generated by default values in /etc/sysctl.conf:
error: "net.bridge.bridge-nf-call-ip6tables" is an unknown key
error: "net.bridge.bridge-nf-call-iptables" is an unknown key
error: "net.bridge.bridge-nf-call-arptables" is an unknown key

Comment 1 Bill Nottingham 2010-07-14 15:18:37 UTC
abrt is the only thing by default that sets core_pattern - assigning there. The *tables errors are unfortunate due to the order of network module loading, and can't be avoided; it's why all scripted invocations of it use '-e'.

Comment 4 RHEL Program Management 2010-07-15 14:45:20 UTC
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release. It has
been denied for the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **

Comment 6 Denys Vlasenko 2010-07-27 11:06:59 UTC
Created bug 618602 - kernel's parameter length limit is too small to fix this bug.

Comment 7 Denys Vlasenko 2010-07-27 11:11:36 UTC
Created attachment 434661 [details]
Proposed patch

Comment 15 Denys Vlasenko 2010-11-22 14:27:43 UTC
Since kernel-side fix (see bug 618602) is planned for inclusion in RHEL6 update,
we are ready to fix it on abrt side too.

Comment 16 Denys Vlasenko 2011-01-06 14:04:07 UTC
Testing the fix for bug 614486 with kernel-2.6.32-83.el6.

I set /proc/sys/kernel/core_pattern to:

echo really_long_long_long_long_long_long_long_long_corename_s%s_c%c_p%p_u%u_g%g_t%t_h%h_e%e >/proc/sys/kernel/core_pattern

When abrt starts, it sets core_pattern to:

|/usr/libexec/abrt-hook-ccpp /var/spool/abrt %s %c %p %u %g %t %h %e 7265616c6c795f6c6f6e675f6c6f6e675f6c6f6e675f6c6f6e675f6c6f6e675f6c6f6e675f6c6f6e675f6c6f6e675f636f72656e616d655f7325735f6325635f7025705f7525755f6725675f7425745f6825685f652565

The long hex string is a hex-encoded "really_long_long_long_long_long_long_long_long_corename_s%s_c%c_p%p_u%u_g%g_t%t_h%h_e%e"

But only "|/usr/libexec/abrt-hook-ccpp /var/spool/abrt %s %c %p %u %g %t %h %e 7265616c6c795f6c6f6e675f6c6f6e675f6c6f6e675f6c6f6e675f6c6f" makes it (127 chars).

As a result, abrt-hook-ccpp saves coredump under truncated name "really_long_long_long_long_lo"

I'd say that for most real-world cases it will work, but raising the 128 char limit would be appreciated.

Comment 17 Denys Vlasenko 2011-01-06 14:47:26 UTC
Fix is pushed to git, abrt_11x branch

Comment 18 Denys Vlasenko 2011-01-06 15:00:34 UTC
Created attachment 472076 [details]
Updated patch (this one went to git)

Comment 25 errata-xmlrpc 2011-05-19 13:41:19 UTC
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 therefore 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.

http://rhn.redhat.com/errata/RHBA-2011-0619.html