Bug 710827

Summary: [abrt] lldpad-0.9.38-1.fc14: strcmp: Process /usr/sbin/lldpad was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Michael Cronenworth <mike>
Component: lldpadAssignee: Petr Šabata <psabata>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: jakub, p.mayers, psabata
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:fbb80e8642407750d87b7830a029305fbe625e59
Fixed In Version: lldpad-0.9.41-4.fc14 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-25 02:13:21 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Michael Cronenworth 2011-06-05 05:42:55 UTC
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 50860 bytes
cmdline: /usr/sbin/lldpad -d
comment: I installed lldpad and attempted to start it for the first time. It crashed. Any subsequent attempt also crashed.
component: lldpad
Attached file: coredump, 385024 bytes
crash_function: strcmp
executable: /usr/sbin/lldpad
kernel: 2.6.35.13-91.fc14.x86_64
package: lldpad-0.9.38-1.fc14
rating: 4
reason: Process /usr/sbin/lldpad was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1307252250
uid: 0

How to reproduce
-----
1. service lldpad start

Comment 1 Michael Cronenworth 2011-06-05 05:43:00 UTC
Created attachment 503045 [details]
File: backtrace

Comment 2 Petr Šabata 2011-06-07 08:19:49 UTC
This is a bug in glibc (__strcmp_sse42), re-assigning.

Comment 3 Andreas Schwab 2011-06-07 08:56:47 UTC
Of course it isn't.

Comment 4 Phil Mayers 2011-09-13 10:28:58 UTC
I see this bug as well.

I'm happy to provide more info, but "this is your bug", "no it's yours" isn't exactly telling me much.

I agree it's not a glibc bug - the offending code seems to be an invalid pointer deref, just prior to calling strcmp in dcb_protocol.c:61, specifically:

#1  0x000000000040d2bc in pg_find (head=<value optimized out>, ifname=0x631cf0 "eth0") at dcb_protocol.c:61
61			if (!strcmp(p->ifname, ifname))

(gdb) print p
$3 = (struct pg_store1 *) 0x1

Comment 5 Michael Cronenworth 2011-09-13 13:01:40 UTC
F15 and higher have a newer version of lldpad. That version does not crash.

Petr, could you push a newer version to F14?

Or are you waiting for F14 to go EOL so this bug will be closed automatically?

Comment 6 Petr Šabata 2011-09-13 13:31:48 UTC
If v0.9.41 (F15 version) fixes the issue for you, I'd be happy to merge F14 branch with it.

F14 0.9.41-4 scratch build:
http://koji.fedoraproject.org/koji/taskinfo?taskID=3348413

Comment 7 Michael Cronenworth 2011-09-13 13:46:53 UTC
The scratch build works fine for me. Thanks, Petr.

Comment 8 Phil Mayers 2011-09-13 13:51:28 UTC
Petr,

Confirmed - the 0.9.41-4 scratch build works on F14 without crashing.

Comment 9 Petr Šabata 2011-09-13 14:09:44 UTC
Thank you both for the confirmation.  I'll push the update.

Comment 10 Fedora Update System 2011-09-13 14:22:27 UTC
lldpad-0.9.41-4.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/lldpad-0.9.41-4.fc14

Comment 11 Fedora Update System 2011-09-14 22:37:34 UTC
Package lldpad-0.9.41-4.fc14:
* should fix your issue,
* was pushed to the Fedora 14 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing lldpad-0.9.41-4.fc14'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/lldpad-0.9.41-4.fc14
then log in and leave karma (feedback).

Comment 12 Fedora Update System 2011-11-25 02:13:21 UTC
lldpad-0.9.41-4.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.