Bug 1697569

Summary: [abrt] ebtables-legacy: dirname(): ebtables-legacy killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Mikhail <mikhail.v.gavrilov>
Component: ebtablesAssignee: Tom "spot" Callaway <tcallawa>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: jpokorny, psutter, tcallawa, twoerner, yaneti
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/2238529375021cb8fa998282ad682c7843499cdb
Whiteboard: abrt_hash:29c3534750be50a56c90661b2254eccaacfdcf3c;VARIANT_ID=workstation;
Fixed In Version: ebtables-2.0.10-34.fc31 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-04-09 13:10:18 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:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: cpuinfo
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status none

Description Mikhail 2019-04-08 17:27:02 UTC 
Version-Release number of selected component:
ebtables-legacy-2.0.10-33.fc31

Additional info:
reporter:       libreport-2.10.0
backtrace_rating: 4
cmdline:        /usr/sbin/ebtables --concurrent -L
crash_function: dirname
executable:     /usr/sbin/ebtables-legacy
journald_cursor: s=2e73494b77804b0ca188d8f6dbd0fd0d;i=17c15f4;b=d0e36c8337e441fbbac05f48f7adfaad;m=458d9716d2;t=58606054ffcc1;x=4133f70baf421e36
kernel:         5.1.0-0.rc3.git1.1.fc31.x86_64
rootdir:        /
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (4 frames)
 #0 dirname at dirname.c:71
 #1 lock_file at libebtc.c:148
 #2 ebt_get_kernel_table at libebtc.c:168
 #3 do_command at ebtables.c:719
Comment 1 Mikhail 2019-04-08 17:27:05 UTC 
Created attachment 1553697 [details]
File: backtrace
Comment 2 Mikhail 2019-04-08 17:27:07 UTC 
Created attachment 1553698 [details]
File: cgroup
Comment 3 Mikhail 2019-04-08 17:27:08 UTC 
Created attachment 1553699 [details]
File: core_backtrace
Comment 4 Mikhail 2019-04-08 17:27:09 UTC 
Created attachment 1553700 [details]
File: cpuinfo
Comment 5 Mikhail 2019-04-08 17:27:10 UTC 
Created attachment 1553701 [details]
File: dso_list
Comment 6 Mikhail 2019-04-08 17:27:11 UTC 
Created attachment 1553702 [details]
File: environ
Comment 7 Mikhail 2019-04-08 17:27:13 UTC 
Created attachment 1553703 [details]
File: exploitable
Comment 8 Mikhail 2019-04-08 17:27:14 UTC 
Created attachment 1553704 [details]
File: limits
Comment 9 Mikhail 2019-04-08 17:27:15 UTC 
Created attachment 1553705 [details]
File: maps
Comment 10 Mikhail 2019-04-08 17:27:16 UTC 
Created attachment 1553706 [details]
File: mountinfo
Comment 11 Mikhail 2019-04-08 17:27:18 UTC 
Created attachment 1553707 [details]
File: open_fds
Comment 12 Mikhail 2019-04-08 17:27:19 UTC 
Created attachment 1553708 [details]
File: proc_pid_status
Comment 13 Jan Pokorný [poki] 2019-04-09 13:07:38 UTC 
Observed this too.
Comment 14 Phil Sutter 2019-04-09 13:09:48 UTC 
Problem caused by a combination of two things:

* Bug in lockfile path customization support (I broke upstream).
* Upstream default lockfile path in build which doesn't exist in Fedora.

Fix sent upstream, Fedora received a new build which restores the old lockfile
location (/run/ebtables.lock) - this effectively avoids the crash, so no need
to wait for upstream fix.