virsh assert failure: *** Error in `virsh': corrupted double-linked list: 0x00007fb69bf98780 ***

Bug #1274995 reported by Marc Deslauriers
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
libvirt (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Has been happening occasionally since i've upgraded to trusty.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: libvirt-bin 1.2.1-0ubuntu5
ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
Uname: Linux 3.13.0-5-generic x86_64
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
AssertionMessage: *** Error in `virsh': corrupted double-linked list: 0x00007fb69bf98780 ***
CrashCounter: 1
CurrentDesktop: Unity
Date: Fri Jan 31 11:21:37 2014
ExecutablePath: /usr/bin/virsh
InstallationDate: Installed on 2013-11-26 (65 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-5-generic.efi.signed root=UUID=daa96c43-a895-4b0f-9a8a-470cf54d2f06 ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: libvirt
StacktraceTop:
 __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7fb699110ec8 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
 malloc_printerr (action=<optimized out>, str=0x7fb69910cf28 "corrupted double-linked list", ptr=<optimized out>) at malloc.c:4924
 _int_free (av=0x7fb69934e760 <main_arena>, p=0x7fb69bf98780, have_lock=0) at malloc.c:3925
 virFree () from /usr/lib/libvirt.so.0
 virObjectUnref () from /usr/lib/libvirt.so.0
Title: virsh assert failure: *** Error in `virsh': corrupted double-linked list: 0x00007fb69bf98780 ***
UpgradeStatus: Upgraded to trusty on 2014-01-17 (13 days ago)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sbuild sudo
modified.conffile..etc.libvirt.qemu.conf: [inaccessible: [Errno 13] Permission denied: '/etc/libvirt/qemu.conf']

Revision history for this message
Marc Deslauriers (mdeslaur) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7fb699110ec8 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
 malloc_printerr (action=<optimized out>, str=0x7fb69910cf28 "corrupted double-linked list", ptr=<optimized out>) at malloc.c:4924
 _int_free (av=0x7fb69934e760 <main_arena>, p=0x7fb69bf98780, have_lock=0) at malloc.c:3925
 virFree (ptrptr=ptrptr@entry=0x7fb694dd0be0) at /build/buildd/libvirt-1.2.1/./src/util/viralloc.c:580
 virObjectUnref (anyobj=<optimized out>) at /build/buildd/libvirt-1.2.1/./src/util/virobject.c:270

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in libvirt (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in libvirt (Ubuntu):
status: New → Confirmed
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

I too see this. For example, it just happened when I installed a 13.10 i386 VM.

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

This looks like it should be fixed by commit 13fdc6d63. I've pushed a package to ppa:serge-hallyn/virt with that commit. Could someone please install it (when it is done building) and see if they can reproduce this?

Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

Serge:

I just got this again with 1.2.1-0ubuntu5. Do you have a test package on top of that somewhere?

Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

hrm, looks like 13fdc6d63 is included in 1.2.1-0ubuntu5...

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

Hi Marc,

I take it this happens randomly, not something you can trigger?

Revision history for this message
Marc Deslauriers (mdeslaur) wrote :

It seems to happen often enough if I launch uvt to update all my vms...I can probably do that a bunch of times in a row if you have a patch you want me to test...

Revision history for this message
Serge Hallyn (serge-hallyn) wrote : Re: [Bug 1274995] Re: virsh assert failure: *** Error in `virsh': corrupted double-linked list: 0x00007fb69bf98780 ***

Thanks Marc - I don't have a patch right now. I'll try to reproduce
using uvt and look for hints

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

Oh, I was thinking uvtool - which doesn't reproduce it for me.

Looking through the stracktrace and the upstream libvirt git tree doesn't show anything promising.

Marc, could you try to reproduce it again with the libvirt that just hit the archive a few minutes ago? Then post a new stackdump here? Also, if you can figure out which particular 'virsh' command is triggering this that'd be helpful. A loop of 1000 sequentil or 8 parallel 'virsh list' didn't do it.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.