Ubuntu16.04.01VM:Docker-Powervm aufs bad file panic while running tests in a docker container
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
New
|
Undecided
|
Seth Forshee |
Bug Description
== Comment: #0 - Vinutha GS - 2016-12-13 02:47:35 ==
When some of the base and io tests were run inside a docker container, the par crashed and below are the stack trace and other details.
Steps to re-create -
1. Install 16.04.02 on a PowerVM lpar.
2. Ran setup general.
3. Ran docker scripts[home grown scripts] which does docker package installation and other setups required to run STAF cases inside docker container.
4. We have docker image using which we launch containers and start tests inside containers.
If complete details are required on how to execute scripts, please let me know.
5. STAF Base and IO tests were started inside containers successfully, after sometime, I see partition is in XMON.
Docker info -
docker info
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 0
Server Version: 1.12.1
Storage Driver: aufs
Root Dir: /var/lib/
Backing Filesystem: extfs
Dirs: 0
Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: null host bridge overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: apparmor
Kernel Version: 4.4.0-53-generic
Operating System: Ubuntu 16.04.1 LTS
OSType: linux
Architecture: ppc64le
CPUs: 24
Total Memory: 49.89 GiB
Name: bamlp3
ID: I7VI:G4RJ:
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https:/
WARNING: No swap limit support
Insecure Registries:
127.0.0.0/8
docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
61f2b8ab0a86 32d545c3ea01 "/bin/sh -c ./staf_io" 24 minutes ago Up 24 minutes bamlp3-io
151da0322172 590e44f15214 "/bin/sh -c ./staf_ba" 30 minutes ago Up 30 minutes bamlp3-base
Stack trace -
8:mon> t
[c000000a5e147d10] d00000000a04ca98 aufs_flush_
[c000000a5e147d40] c0000000002e0428 filp_close+
[c000000a5e147dc0] c00000000030f71c __close_
[c000000a5e147e00] c0000000002e04d4 SyS_close+0x34/0x90
[c000000a5e147e30] c000000000009204 system_
--- Exception: c00 (System Call) at 00003fff8bc217d8
SP (3fffd85203b0) is in userspace
8:mon> e
cpu 0x8: Vector: 300 (Data Access) at [c000000a5e147a40]
pc: d00000000a04bdd4: au_do_flush+
lr: d00000000a04ca98: aufs_flush_
sp: c000000a5e147cc0
msr: 8000000000009033
dar: 28
dsisr: 40000000
current = 0xc000000a8b7fc8e0
paca = 0xc00000000fb44c00 softe: 0 irq_happened: 0x01
pid = 11936, comm = remap_file_page
8:mon>
Release details -
uname -r
4.4.0-53-generic
uname -a
Linux bamlp4 4.4.0-53-generic #74-Ubuntu SMP Fri Dec 2 15:59:36 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
== Comment: #6 - Vinutha GS - 2016-12-14 03:16:18 ==
Please find the attached sosreport.
Also i have followed the steps for k-dump, It is enabled now.
I'm going to start the tests once again.
== Comment: #12 - Kevin W. Rudd - 2016-12-14 16:06:46 ==
The basic reason for the panic is that close was called on a file
that was no longer valid. The f_count value was -8 for some reason,
so it passed the following check in filep_close():
if (!file_count(filp)) {
}
It then blew up in au_do_flush() because f_inode was NULL.
Changed in linux (Ubuntu): | |
assignee: | Taco Screen team (taco-screen-team) → Seth Forshee (sforshee) |
tags: |
added: severity-high removed: severity-critical |
Default Comment by Bridge