[Bug libc/10051] New: segfault with libc and qemu when socket listen used

[Bug libc/10051] New: segfault with libc and qemu when socket listen used

[patatetom at gmail dot com]

Hi,

On Arch Linux...

Description:

Starting qemu or kvm with "-net socket,listen=:1234" option crash with
segmentation fault.
In /var/log/everything.log : "kernel: qemu[5852]: segfault at 0 ip b7bf8063 sp
bfee197c error 4 in libc-2.9.so[b7b85000+140000]"

Additional info:
* package version(s)
* config and/or log files etc.

qemu | grep version
QEMU PC emulator version 0.10.2, Copyright (c) 2003-2008 Fabrice Bellard

pacman -Qs | grep glibc
local/glibc 2.9-4 (base)

Steps to reproduce:

qemu -k fr -cdrom ~/debian-500-i386-DVD-1.iso -net nic -net socket,listen=:12345
or
qemu -enable-kvm -k fr -cdrom ~/debian-500-i386-DVD-1.iso -net nic -net
socket,listen=:12345


The bug is already reported in bug section on Arch Linux home.

-- 
           Summary: segfault with libc and qemu when socket listen used
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
        AssignedTo: drepper at redhat dot com
        ReportedBy: patatetom at gmail dot com
                CC: glibc-bugs at sources dot redhat dot com
 GCC build triplet: 2.9-4
  GCC host triplet: 2.6.29


http://sourceware.org/bugzilla/show_bug.cgi?id=10051

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug libc/10051] segfault with libc and qemu when socket listen used

[patatetom at gmail dot com]

------- Additional Comments From patatetom at gmail dot com  2009-04-10 19:40 -------
This is a probably not a bug for libc but for qemu : see comment by Gerardo
Exequiel Pozzi at http://bugs.archlinux.org/task/13754 

(In reply to comment #0)
> Hi,
> 
> On Arch Linux...
> 
> Description:
> 
> Starting qemu or kvm with "-net socket,listen=:1234" option crash with
> segmentation fault.
> In /var/log/everything.log : "kernel: qemu[5852]: segfault at 0 ip b7bf8063 sp
> bfee197c error 4 in libc-2.9.so[b7b85000+140000]"
> 
> Additional info:
> * package version(s)
> * config and/or log files etc.
> 
> qemu | grep version
> QEMU PC emulator version 0.10.2, Copyright (c) 2003-2008 Fabrice Bellard
> 
> pacman -Qs | grep glibc
> local/glibc 2.9-4 (base)
> 
> Steps to reproduce:
> 
> qemu -k fr -cdrom ~/debian-500-i386-DVD-1.iso -net nic -net socket,listen=:12345
> or
> qemu -enable-kvm -k fr -cdrom ~/debian-500-i386-DVD-1.iso -net nic -net
> socket,listen=:12345
> 
> 
> The bug is already reported in bug section on Arch Linux home.



-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |SUSPENDED


http://sourceware.org/bugzilla/show_bug.cgi?id=10051

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug libc/10051] segfault with libc and qemu when socket listen used

[pasky at suse dot cz]

------- Additional Comments From pasky at suse dot cz  2010-06-01 04:07 -------
No glibc bug, thus closing.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|SUSPENDED                   |RESOLVED
         Resolution|                            |INVALID


http://sourceware.org/bugzilla/show_bug.cgi?id=10051

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

[Bug libc/10051] segfault with libc and qemu when socket listen used

[fweimer at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=10051

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|                            |security-

-- 
You are receiving this mail because:
You are on the CC list for the bug.