Bug 493622 - ss segfaults when ipv6 is disabled
Summary: ss segfaults when ipv6 is disabled
Keywords:
Status: CLOSED DUPLICATE of bug 493578
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: iproute
Version: 5.3
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Marcela Mašláňová
QA Contact: BaseOS QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-04-02 12:43 UTC by Ralph Angenendt
Modified: 2009-04-07 09:27 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-04-07 09:27:26 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
CentOS 3475 0 None None None Never

Description Ralph Angenendt 2009-04-02 12:43:25 UTC
Description of problem:

When using the ss binary from the iproute package on a machine with ipv6 disabled, ss segfaults.

Version-Release number of selected component (if applicable):

iproute-2.6.18-10.el5

How reproducible:

Always

Steps to Reproduce:

[root@localhost ~]# ss
State      Recv-Q Send-Q      Local Address:Port          Peer Address:Port   
Segmentation fault
[root@localhost ~]# strace ss
execve("/usr/sbin/ss", ["ss"], [/* 17 vars */]) = 0
brk(0)                                  = 0x856b000
access("/etc/ld.so.preload", R_OK)      = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY)      = 3

[...]
close(4)                                = 0
open("/proc/net/tcp6", O_RDONLY)        = -1 ENOENT (No such file or directory)
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++

[root@localhost ~]# rm /etc/modprobe.d/disable-ipv6 && modprobe ipv6
[root@localhost ~]# ss
State      Recv-Q Send-Q      Local Address:Port          Peer Address:Port   
[root@localhost ~]# exit

Actual results:

ss segfaults

Expected results:

ss does not segfault

Comment 1 Marcela Mašláňová 2009-04-07 09:27:26 UTC

*** This bug has been marked as a duplicate of bug 493578 ***


Note You need to log in before you can comment on or make changes to this bug.