auplink crashed with SIGSEGV in fts_build()

Bug #1561570 reported by Scott Stensland on 2016-03-24
432
This bug affects 155 people
Affects Status Importance Assigned to Milestone
aufs-tools (Ubuntu)
Medium
Unassigned

Bug Description

Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04

aufs-tools:
  Installed: 1:3.2+20130722-1.1ubuntu1
  Candidate: 1:3.2+20130722-1.1ubuntu1
  Version table:
 *** 1:3.2+20130722-1.1ubuntu1 500
        500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
        100 /var/lib/dpkg/status

I get this on boot up prior to launching anything

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: aufs-tools 1:3.2+20130722-1.1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
Uname: Linux 4.4.0-15-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Tue Mar 22 17:28:55 2016
Dependencies:
 gcc-6-base 6-20160319-0ubuntu1
 libc6 2.23-0ubuntu2
 libgcc1 1:6-20160319-0ubuntu1
ExecutablePath: /sbin/auplink
InstallationDate: Installed on 2016-03-22 (2 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
ProcCmdline: auplink /var/lib/docker/aufs/mnt/1bfcf47905540d3777c3e4b5fec20edd21bcef13490744d238b5a1c582d9ce88 flush
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x7f4845939009 <fts_build+1289>: (bad)
 PC (0x7f4845939009) ok
 SP (0x7ffc026a2430) not located in a known VMA region (needed readable region)!
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: aufs-tools
StacktraceTop: fts_build (sp=0x13, type=<error reading variable: Cannot access memory at address 0x7ffc026a2498>) at ../sysdeps/wordsize-64/../../io/fts.c:799
Title: auplink crashed with SIGSEGV in fts_build()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

information type: Private → Public

StacktraceSource:
 #0 0x00007f4845939009 in fts_build (sp=0x13, sp@entry=<error reading variable: Cannot access memory at address 0x7ffc026a2568>, type=<error reading variable: Cannot access memory at address 0x7ffc026a2498>, type@entry=<error reading variable: Cannot access memory at address 0x7ffc026a2568>) at ../sysdeps/wordsize-64/../../io/fts.c:799
   [Error: fts.c was not found in source tree]
StacktraceTop: fts_build (sp=0x13, sp@entry=<error reading variable: Cannot access memory at address 0x7ffc026a2568>, type=<error reading variable: Cannot access memory at address 0x7ffc026a2498>, type@entry=<error reading variable: Cannot access memory at address 0x7ffc026a2568>) at ../sysdeps/wordsize-64/../../io/fts.c:799

Changed in aufs-tools (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Launchpad Janitor (janitor) wrote :

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

Changed in aufs-tools (Ubuntu):
status: New → Confirmed
Danijel (dadoghost) wrote :

This report seems to be a duplicate of 1442892 and 1502837. But can't be marked as duplicate because of:

Bug 1502837 is already a duplicate of bug 1442892. You can only mark a bug report as duplicate of one that isn&#x27;t a duplicate itself.

Martin (mselke) on 2017-09-20
information type: Public → Public Security
Craig Jellick (craig-jellick) wrote :

If this affects you and you are using aufs as your docker storage driver just because it is the default, you can just switch to the overlay2 storage driver to circumvent this crash.

Note that switching storage drivers will cause you to "lose" all you docker images. You'll have to repull them.

Can switch the storage driver on ubuntu (w/systemd) by putting this:
```
{
    "storage-driver": "overlay2"
}
```
in /etc/docker/daemon.json and restarting docker.

I can confirm your fix worked.

 apt-cache policy docker-engine
docker-engine:
  Installed: 17.05.0~ce~rc3-0~ubuntu-zesty

 docker info
Containers: 7
 Running: 6
 Paused: 0
 Stopped: 1
Images: 174
Server Version: 17.05.0-ce-rc3
Storage Driver: overlay2
 Backing Filesystem: extfs
 Supports d_type: true
 Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 9048e5e50717ea4497b757314bad98ea3763c145
runc version: 9c2d8d184e5da67c95d601382adf14862e4f2228
init version: 949e6fa
Security Options:
 apparmor
 seccomp
  Profile: default
Kernel Version: 4.13.0-11-generic
Operating System: Ubuntu Artful Aardvark (development branch)
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 11.61GiB
Name: cameroon
ID: EJ4H:WXHF:GKCB:KO52:6EE2:BXWZ:5IFC:AM7K:CT5C:VB4P:Y7VI:JTMX
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Experimental: false
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false

uname -m && uname -r && cat /etc/*release
x86_64
4.13.0-11-generic
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=17.10
DISTRIB_CODENAME=artful
DISTRIB_DESCRIPTION="Ubuntu Artful Aardvark (development branch)"
NAME="Ubuntu"
VERSION="17.10 (Artful Aardvark)"

apt-cache policy aufs-tools
aufs-tools:
  Installed: 1:3.2+20130722-1.1ubuntu1

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

Other bug subscribers