auplink crashed with SIGSEGV in ftw_startup()

Bug #1502837 reported by Steyn Geldenhuys on 2015-10-05
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
aufs-tools (Ubuntu)
Undecided
Unassigned

Bug Description

On startup of my 15.10 beta 2 machine I got this error.

ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: aufs-tools 1:3.2+20130722-1.1
ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
Uname: Linux 4.2.0-14-generic x86_64
ApportVersion: 2.19-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Mon Oct 5 08:15:49 2015
Dependencies:
 gcc-5-base 5.2.1-20ubuntu1
 libc6 2.21-0ubuntu4
 libgcc1 1:5.2.1-20ubuntu1
ExecutablePath: /sbin/auplink
InstallationDate: Installed on 2015-10-03 (1 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
ProcCmdline: auplink /var/lib/docker/aufs/mnt/1b7e08ba8126f15aff61025908978c6ef861da865811d9dfc0cc541b73c6e5e1 flush
ProcEnviron:
 LANG=en_ZA.UTF-8
 LANGUAGE=en_ZA:en
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x7f8bdba9b759 <ftw_startup+105>: callq 0x7f8bdba31200 <__memset_sse2>
 PC (0x7f8bdba9b759) ok
 source "0x7f8bdba31200" (0x7f8bdba31200) ok
 destination "(%rsp)" (0x7ffeb9b57380) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: aufs-tools
StacktraceTop:
 ftw_startup (dir=0x608010 "/var/lib/docker/aufs/mnt/1b7e08ba8126f15aff61025908978c6ef861da865811d9dfc0cc541b73c6e5e1", is_nftw=1, func=0x401458, descriptors=1048566, flags=19) at ../sysdeps/wordsize-64/../../io/ftw.c:654
 ?? ()
 ?? ()
 __libc_start_main (main=0x40126d, argc=3, argv=0x7ffeba357668, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffeba357658) at libc-start.c:289
 ?? ()
Title: auplink crashed with SIGSEGV in ftw_startup()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1441038, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-amd64-retrace
Conor (mcgeeco) wrote :

Why is there a bot going around marking all these as duplicates of a deleted bug?

Launchpad Janitor (janitor) wrote :

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

Changed in aufs-tools (Ubuntu):
status: New → Confirmed
Ville Ranki (ville-ranki) wrote :

I changed the duplicate status to a more suitable bug ticket. I hope this is fixed soon.

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

Other bug subscribers