Docker causes a segfault when starting containers

Bug #1442568 reported by Jordon Bedwell on 2015-04-10
This bug affects 10 people
Affects Status Importance Assigned to Milestone
aufs-tools (Ubuntu)

Bug Description

[ 5543.639966] auplink[32506]: \
  segfault at 7ffd7a033578 ip 00007f04f6079759 sp 00007ffd7a033580 error 6 in \[7f04f5f80000+1c0000]

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: aufs-tools 1:3.2+20130722-1.1
ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3
Uname: Linux 3.19.0-12-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.17-0ubuntu1
Architecture: amd64
Date: Fri Apr 10 04:24:35 2015
 gcc-5-base 5-20150401-0ubuntu1
 libc6 2.21-0ubuntu4
 libgcc1 1:5-20150401-0ubuntu1
 multiarch-support 2.21-0ubuntu4
ExecutablePath: /sbin/auplink
InstallationDate: Installed on 2015-04-09 (0 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
ProcCmdline: auplink /var/lib/docker/aufs/mnt/62bd6e5d31017cc82dc68b8515d176ce3998720370c03a987a658d340530d75e flush
 PATH=(custom, no user)
SegvAnalysis: Skipped: missing required field "Disassembly"
Signal: 11
SourcePackage: aufs-tools
UpgradeStatus: Upgraded to vivid on 2015-04-09 (0 days ago)

Revision history for this message
Jordon Bedwell (envygeeks) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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
Revision history for this message
Blake Mitchell (ubuntu-com-z) wrote :

The linked bug is private, are there any known work-arounds for this issue?

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in aufs-tools (Ubuntu):
status: New → Confirmed
Revision history for this message
Sławek Ehlert (slafs) wrote :

bug #1441038 no longer exists. Is there a new one we could follow?

Revision history for this message
Christopher Hall (hsw) wrote :

Also interest to know what happened to bug #1441038 (or is this number incorrect?)

Revision history for this message
Jordon Bedwell (envygeeks) wrote :

The duplicate link has been removed.

Revision history for this message
Christopher Hall (hsw) wrote :

OK, I just wondered if there were additional details.
I looked at aufs_utils, and it look like the problem is with the AUFin macro (au_util.h)which is

#define AuFin(fmt, ...) \
        error_at_line(errno, errno, __FILE__, __LINE__, fmt, ##__VA_ARGS__)

I think this should be:

#define AuFin(fmt, ...) \
        error_at_line(1, errno, __FILE__, __LINE__, fmt, ##__VA_ARGS__)

The value 1 for the status parameter would always ensure program termination rather than the
current situation where it will continue (if errno == 0) and proceed to segfault or some other crash.

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

Other bug subscribers