Bug 696509

Summary: [abrt] omping-0.0.1-2.fc14: af_find_local_ai: Process /usr/bin/omping was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: David Juran <djuran>
Component: ompingAssignee: Jan Friesse <jfriesse>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: jfriesse, mglantz
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:b0bbfc6a6ba2f2b5bc1f8beb8f0992dbc6fa4f92
Fixed In Version: omping-0.0.1-3.fc14 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-20 03:22:59 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
Proposed patch - in git none

Description David Juran 2011-04-14 07:50:11 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 12271 bytes
cmdline: omping 224.0.0.251
comment: Yes, I know it's silly and wrong, but it still shouldn't crash...
component: omping
Attached file: coredump, 372736 bytes
crash_function: af_find_local_ai
executable: /usr/bin/omping
kernel: 2.6.35.12-88.fc14.x86_64
package: omping-0.0.1-2.fc14
rating: 4
reason: Process /usr/bin/omping was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1302767173
uid: 500

How to reproduce
-----
1.  omping 224.0.0.251

Comment 1 David Juran 2011-04-14 07:50:14 UTC
Created attachment 491980 [details]
File: backtrace

Comment 2 David Juran 2011-04-14 08:49:12 UTC
Package: omping-0.0.1-2.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.  omping -m ALL-SYSTEMS.MCAST.NET 192.168.255.2 192.168.122.239

Comment 3 Jan Friesse 2011-04-14 10:15:08 UTC
Hi David,
I'm not able to reproduce bug in my testing environment. Can you please rerun with -vvv and send me output? Also valgrind output may be helpful.

Thanks,
  Jan

Comment 4 Jan Friesse 2011-04-14 11:48:14 UTC
David,
I was able to reproduce bug. It seems that you are using ppp interface without IP assigned and pointer to ifa_addr (NULL) is dereferenced.

Fix included in next comment.

Thanks for report,
  Jan

Comment 5 Jan Friesse 2011-04-14 11:58:36 UTC
Created attachment 492076 [details]
Proposed patch - in git

Patch is included in git as 220749b10250154f95aa05c8b948cbe7015a2daa

Comment 6 Magnus Glantz 2011-04-14 12:05:50 UTC
Package: omping-0.0.1-2.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Start a mcast listner on 224.0.0.1 port 5000.
2. Run omping -i 1 -m 224.0.0.1 -p 5000 <IP_ADDR>
3. Segmentation fault (core dumped)

Comment 7 Fedora Update System 2011-04-14 12:53:35 UTC
omping-0.0.1-3.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/omping-0.0.1-3.fc14

Comment 8 Fedora Update System 2011-04-14 12:57:21 UTC
omping-0.0.2-3.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/omping-0.0.2-3.fc15

Comment 9 Magnus Glantz 2011-04-14 16:53:28 UTC
The update fixed the issue for me.

Comment 10 Fedora Update System 2011-04-14 20:52:46 UTC
Package omping-0.0.1-3.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 omping-0.0.1-3.fc14'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/omping-0.0.1-3.fc14
then log in and leave karma (feedback).

Comment 11 Fedora Update System 2011-04-20 03:22:55 UTC
omping-0.0.2-3.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 12 Fedora Update System 2011-04-22 21:17:36 UTC
omping-0.0.1-3.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.