udisksd crashed with SIGSEGV in g_variant_unref()

Bug #1032371 reported by Ana Katalinova
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
udisks2 (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

no idea!

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: udisks2 1.99.0-1
ProcVersionSignature: Ubuntu 3.5.0-6.6-generic 3.5.0
Uname: Linux 3.5.0-6-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.4-0ubuntu6
Architecture: amd64
Date: Thu Aug 2 14:38:43 2012
ExecutablePath: /usr/lib/udisks2/udisksd
InstallationMedia: This
MachineType: Acer Aspire 5943G
ProcCmdline: /usr/lib/udisks2/udisksd --no-debug
ProcEnviron:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-6-generic root=UUID=021d2b15-ed4b-42bb-9a9a-c80dd3b92989 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7
SegvAnalysis:
 Segfault happened at: 0x7f29298dd98d <g_variant_unref+13>: mov 0x24(%rdi),%eax
 PC (0x7f29298dd98d) ok
 source "0x24(%rdi)" (0xaaaaaaaaaaaaaace) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: udisks2
StacktraceTop:
 g_variant_unref () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
 ?? ()
 ?? ()
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: udisksd crashed with SIGSEGV in g_variant_unref()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 10/21/2010
dmi.bios.vendor: Acer
dmi.bios.version: V1.15
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Aspire 5943G
dmi.board.vendor: Acer
dmi.board.version: V1.15
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.15
dmi.modalias: dmi:bvnAcer:bvrV1.15:bd10/21/2010:svnAcer:pnAspire5943G:pvrV1.15:rvnAcer:rnAspire5943G:rvrV1.15:cvnAcer:ct10:cvrV1.15:
dmi.product.name: Aspire 5943G
dmi.product.version: V1.15
dmi.sys.vendor: Acer

Revision history for this message
Ana Katalinova (katalinova) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_variant_unref (value=0xaaaaaaaaaaaaaaaa) at /build/buildd/glib2.0-2.33.6/./glib/gvariant-core.c:622
 udisks_linux_drive_ata_refresh_smart_sync (drive=0x208b3f0, nowakeup=nowakeup@entry=0, simulate_path=simulate_path@entry=0x0, cancellable=cancellable@entry=0x0, error=error@entry=0x7f29275c7d48) at udiskslinuxdriveata.c:555
 udisks_linux_drive_object_housekeeping (object=object@entry=0x2088d60, secs_since_last=secs_since_last@entry=0, cancellable=cancellable@entry=0x0, error=error@entry=0x7f29275c7d98) at udiskslinuxdriveobject.c:926
 perform_initial_housekeeping_for_drive (job=<optimized out>, cancellable=<optimized out>, user_data=<optimized out>) at udiskslinuxprovider.c:439
 io_job_thread (data=0x20b2d30, user_data=<optimized out>) at /build/buildd/glib2.0-2.33.6/./gio/gioscheduler.c:168

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 udisks2 (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in udisks2 (Ubuntu):
status: New → Confirmed
Martin Pitt (pitti)
visibility: private → public
Revision history for this message
Martin Pitt (pitti) wrote :

It crashes in udisks_linux_drive_ata_refresh_smart_sync(), called through the 10-minute "housekeeping" thread. drive->smart_attributes is already invalid (0xaaaa...). I figure what happens here is that the drive went away at the same time as the regular SMART update kicked in, and drive->smart_attributes already got unreffed by udisks_linux_drive_ata_finalize().

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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