Kernel panic on btrfs mount and ls

Bug #1587475 reported by Destitutus
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
High
Unassigned
Xenial
Confirmed
High
Dragan S.

Bug Description

Kernel panic happens after mount and ls specific btrfs image

Way to reproduce:
1. download and unpack btrfs image from tar(sparse file)(tar -Sxf img.tar)
2. mount btrfs (sudo mount -t btrfs -o rw,noatime,compress=no,commit=5 71bb49cf-26f1-484a-832c-e966f43adca9.img broken)
3. list files in mount point (ls -al broken)

the system down to kernel panic with log above

(looks like 3.19.x and 4.2.x not affected, only 4.4.x)

dmesg log:
May 31 13:02:21 fs-new kernel: [ 694.744630] BTRFS error (device loop0): parent transid verify failed on 30425088 wanted 120 found 119
May 31 13:02:21 fs-new kernel: [ 694.747077] BTRFS error (device loop0): parent transid verify failed on 30425088 wanted 120 found 119
May 31 13:02:21 fs-new kernel: [ 694.747128] ------------[ cut here ]------------
May 31 13:02:21 fs-new kernel: [ 694.747135] WARNING: CPU: 0 PID: 13795 at /build/linux-lts-xenial-7RlTta/linux-lts-xenial-4.4.0/lib/idr.c:1051 ida_remove+0xfa/0x130()
May 31 13:02:21 fs-new kernel: [ 694.747136] ida_remove called for id=47 which is not allocated.
May 31 13:02:21 fs-new kernel: [ 694.747137] Modules linked in: ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c nfsv3 vboxsf xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack zram lz4_compress xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables autofs4 ppdev vboxvideo ttm crct10dif_pclmul crc32_pclmul drm_kms_helper drm aesni_intel aes_x86_64 lrw input_leds gf128mul nfsd glue_helper ablk_helper cryptd auth_rpcgss serio_raw nfs_acl nfs fb_sys_fops syscopyarea lockd sysfillrect grace 8250_fintek parport_pc sysimgblt vboxguest i2c_piix4 sunrpc video mac_hid fscache lp parport zfs(POE) zunicode(POE) zcommon(POE) znvpair(POE) spl(OE) zavl(POE) btrfs xor raid6_pq psmouse e1000 fjes pata_acpi
May 31 13:02:21 fs-new kernel: [ 694.747182] CPU: 0 PID: 13795 Comm: ls Tainted: P OE 4.4.0-22-generic #40~14.04.1-Ubuntu
May 31 13:02:21 fs-new kernel: [ 694.747183] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
May 31 13:02:21 fs-new kernel: [ 694.747185] 0000000000000000 ffff8800024e7a88 ffffffff813cde6c ffff8800024e7ad0
May 31 13:02:21 fs-new kernel: [ 694.747187] ffffffff81af5298 ffff8800024e7ac0 ffffffff8107d856 0000000000000000
May 31 13:02:21 fs-new kernel: [ 694.747189] ffffffff81fce200 ffff88003c827a00 ffff88003616e068 0000000000000001
May 31 13:02:21 fs-new kernel: [ 694.747191] Call Trace:
May 31 13:02:21 fs-new kernel: [ 694.747195] [<ffffffff813cde6c>] dump_stack+0x63/0x87
May 31 13:02:21 fs-new kernel: [ 694.747199] [<ffffffff8107d856>] warn_slowpath_common+0x86/0xc0
May 31 13:02:21 fs-new kernel: [ 694.747201] [<ffffffff8107d8dc>] warn_slowpath_fmt+0x4c/0x50
May 31 13:02:21 fs-new kernel: [ 694.747214] [<ffffffff811a337a>] ? free_percpu+0xba/0x180
May 31 13:02:21 fs-new kernel: [ 694.747217] [<ffffffff813cef0a>] ida_remove+0xfa/0x130
May 31 13:02:21 fs-new kernel: [ 694.747220] [<ffffffff811fff4c>] free_anon_bdev+0x2c/0x50
May 31 13:02:21 fs-new kernel: [ 694.747239] [<ffffffffc00f234e>] free_fs_root+0xbe/0xe0 [btrfs]
May 31 13:02:21 fs-new kernel: [ 694.747251] [<ffffffffc00f3b96>] btrfs_get_fs_root+0x216/0x250 [btrfs]
May 31 13:02:21 fs-new kernel: [ 694.747264] [<ffffffffc011d92d>] ? memcmp_extent_buffer+0xbd/0x120 [btrfs]
May 31 13:02:21 fs-new kernel: [ 694.747277] [<ffffffffc0106e4c>] btrfs_lookup_dentry+0x28c/0x4c0 [btrfs]
May 31 13:02:21 fs-new kernel: [ 694.747288] [<ffffffffc0107092>] btrfs_lookup+0x12/0x40 [btrfs]
May 31 13:02:21 fs-new kernel: [ 694.747291] [<ffffffff8120716d>] lookup_real+0x1d/0x50
May 31 13:02:21 fs-new kernel: [ 694.747293] [<ffffffff81207523>] __lookup_hash+0x33/0x40
May 31 13:02:21 fs-new kernel: [ 694.747295] [<ffffffff81209a47>] walk_component+0x177/0x280
May 31 13:02:21 fs-new kernel: [ 694.747297] [<ffffffff8125c0d9>] ? posix_acl_xattr_get+0x49/0xb0
May 31 13:02:21 fs-new kernel: [ 694.747299] [<ffffffff8120ae80>] path_lookupat+0x60/0x110
May 31 13:02:21 fs-new kernel: [ 694.747301] [<ffffffff8120ca4c>] filename_lookup+0x9c/0x150
May 31 13:02:21 fs-new kernel: [ 694.747304] [<ffffffff811dbc2f>] ? kmem_cache_alloc+0x19f/0x200
May 31 13:02:21 fs-new kernel: [ 694.747306] [<ffffffff8120c68f>] ? getname_flags+0x4f/0x1f0
May 31 13:02:21 fs-new kernel: [ 694.747308] [<ffffffff8120cbb6>] user_path_at_empty+0x36/0x40
May 31 13:02:21 fs-new kernel: [ 694.747310] [<ffffffff81202523>] vfs_fstatat+0x53/0xa0
May 31 13:02:21 fs-new kernel: [ 694.747312] [<ffffffff812029e2>] SYSC_newlstat+0x22/0x40
May 31 13:02:21 fs-new kernel: [ 694.747315] [<ffffffff8121cf04>] ? mntput+0x24/0x40
May 31 13:02:21 fs-new kernel: [ 694.747317] [<ffffffff812071be>] ? path_put+0x1e/0x30
May 31 13:02:21 fs-new kernel: [ 694.747318] [<ffffffff812220e2>] ? path_getxattr+0x62/0x90
May 31 13:02:21 fs-new kernel: [ 694.747321] [<ffffffff81202bfe>] SyS_newlstat+0xe/0x10
May 31 13:02:21 fs-new kernel: [ 694.747324] [<ffffffff817efcf6>] entry_SYSCALL_64_fastpath+0x16/0x75
May 31 13:02:21 fs-new kernel: [ 694.747326] ---[ end trace 5c7309d2219a269a ]---
May 31 13:02:21 fs-new kernel: [ 694.761474] Modules linked in: ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c nfsv3 vboxsf xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack zram lz4_compress xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables autofs4 ppdev vboxvideo ttm crct10dif_pclmul crc32_pclmul drm_kms_helper drm aesni_intel aes_x86_64 lrw input_leds gf128mul nfsd glue_helper ablk_helper cryptd auth_rpcgss serio_raw nfs_acl nfs fb_sys_fops syscopyarea lockd sysfillrect grace 8250_fintek parport_pc sysimgblt vboxguest i2c_piix4 sunrpc video mac_hid fscache lp parport zfs(POE) zunicode(POE) zcommon(POE) znvpair(POE) spl(OE) zavl(POE) btrfs xor raid6_pq psmouse e1000 fjes pata_acpi
May 31 13:02:21 fs-new kernel: [ 694.763145] CPU: 0 PID: 13581 Comm: zsh Tainted: P W OE 4.4.0-22-generic #40~14.04.1-Ubuntu
May 31 13:02:21 fs-new kernel: [ 694.763207] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
May 31 13:02:21 fs-new kernel: [ 694.763261] task: ffff880038485280 ti: ffff88001c104000 task.ti: ffff88001c104000
May 31 13:02:21 fs-new kernel: [ 694.763307] RIP: 0010:[<ffffffff811dbb09>] [<ffffffff811dbb09>] kmem_cache_alloc+0x79/0x200
May 31 13:02:21 fs-new kernel: [ 694.763654] RSP: 0018:ffff88001c107d38 EFLAGS: 00010282
May 31 13:02:21 fs-new kernel: [ 694.763689] RAX: 0000000000000000 RBX: 0000000002000200 RCX: 00000000005306fe
May 31 13:02:21 fs-new kernel: [ 694.763733] RDX: 00000000005306fd RSI: 0000000002000200 RDI: ffff88003c801b00
May 31 13:02:21 fs-new kernel: [ 694.763777] RBP: ffff88001c107d68 R08: 0000000000019f80 R09: ffffffff811bda0d
May 31 13:02:21 fs-new kernel: [ 694.763820] R10: 0000000000000000 R11: ffffffff81ac9018 R12: 0000000002000200
May 31 13:02:21 fs-new kernel: [ 694.763862] R13: 53f000ff53f000ff R14: ffff88003c801b00 R15: ffff88003c801b00
May 31 13:02:21 fs-new kernel: [ 694.763908] FS: 00007f73347c4740(0000) GS:ffff88003e400000(0000) knlGS:0000000000000000
May 31 13:02:21 fs-new kernel: [ 694.763958] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
May 31 13:02:21 fs-new kernel: [ 694.763993] CR2: 0000000000ec7ba8 CR3: 0000000002445000 CR4: 00000000000406f0
May 31 13:02:21 fs-new kernel: [ 694.764043] Stack:
May 31 13:02:21 fs-new kernel: [ 694.764059] ffffffff81fc7220 ffff88001c0807d0 ffff880002440380 0000000000000000
May 31 13:02:21 fs-new kernel: [ 694.764113] 0000000000000001 ffff880035ea3a98 ffff88001c107dc0 ffffffff811bda0d
May 31 13:02:21 fs-new kernel: [ 694.764166] ffff88000241e4b0 ffff88001c080848 ffff88000241e528 0000000000000000
May 31 13:02:21 fs-new kernel: [ 694.764219] Call Trace:
May 31 13:02:21 fs-new kernel: [ 694.764243] [<ffffffff811bda0d>] anon_vma_clone+0x6d/0x1f0
May 31 13:02:21 fs-new kernel: [ 694.764280] [<ffffffff811bdbc0>] anon_vma_fork+0x30/0x130
May 31 13:02:21 fs-new kernel: [ 694.766727] [<ffffffff8107bcf6>] copy_process+0xe36/0x1c60
May 31 13:02:21 fs-new kernel: [ 694.767979] [<ffffffff8107cc92>] _do_fork+0x82/0x310
May 31 13:02:21 fs-new kernel: [ 694.771206] [<ffffffff8108c931>] ? sigprocmask+0x51/0x80
May 31 13:02:21 fs-new kernel: [ 694.774372] [<ffffffff8107cfc9>] SyS_clone+0x19/0x20
May 31 13:02:21 fs-new kernel: [ 694.775874] [<ffffffff817efcf6>] entry_SYSCALL_64_fastpath+0x16/0x75
May 31 13:02:21 fs-new kernel: [ 694.776895] Code: 4c 03 05 83 e6 e2 7e 4d 8b 28 49 8b 40 10 4d 85 ed 0f 84 43 01 00 00 48 85 c0 0f 84 3a 01 00 00 49 63 46 20 48 8d 4a 01 4d 8b 06 <49> 8b 5c 05 00 4c 89 e8 65 49 0f c7 08 0f 94 c0 84 c0 74 b8 49
May 31 13:02:21 fs-new kernel: [ 694.779447] RIP [<ffffffff811dbb09>] kmem_cache_alloc+0x79/0x200
May 31 13:02:21 fs-new kernel: [ 694.780143] RSP <ffff88001c107d38>
May 31 13:02:21 fs-new kernel: [ 694.780965] fbcon_switch: detected unhandled fb_set_par error, error code -16
May 31 13:02:21 fs-new kernel: [ 694.782726] fbcon_switch: detected unhandled fb_set_par error, error code -16
May 31 13:02:21 fs-new kernel: [ 694.784621] ---[ end trace 5c7309d2219a269b ]---

Kernel: Ubuntu 4.4.0-22.40~14.04.1-generic 4.4.8
Release: Description: Ubuntu 14.04.3 LTS, Release: 14.04
Btrfs-tools version:
Installed: 3.12-1
  Candidate: 3.12-1ubuntu0.1
  Version table:
     3.12-1ubuntu0.1 0
        500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
 *** 3.12-1 0
        500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
        100 /var/lib/dpkg/status
---
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116, 1 May 31 13:46 seq
 crw-rw---- 1 root audio 116, 33 May 31 13:46 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=/dev/mapper/packer--virtualbox--iso--1443437048--vg-swap_1
InstallationDate: Installed on 2015-09-28 (246 days ago)
InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99
MachineType: innotek GmbH VirtualBox
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
Package: linux (not installed)
PciMultimedia:

ProcFB: 0 vboxdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/packer--virtualbox--iso--1443437048--vg-root ro debian-installer=en_US cgroup_enable=memory swapaccount=1 quiet
ProcVersionSignature: Ubuntu 4.4.0-22.40~14.04.1-generic 4.4.8
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-22-generic N/A
 linux-backports-modules-4.4.0-22-generic N/A
 linux-firmware 1.127.14
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty
Uname: Linux 4.4.0-22-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

Revision history for this message
Destitutus (didrive) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1587475

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: trusty
Revision history for this message
Destitutus (didrive) wrote : BootDmesg.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Destitutus (didrive) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Destitutus (didrive) wrote : Lspci.txt

apport information

Revision history for this message
Destitutus (didrive) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Destitutus (didrive) wrote : ProcEnviron.txt

apport information

Revision history for this message
Destitutus (didrive) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Destitutus (didrive) wrote : ProcModules.txt

apport information

Revision history for this message
Destitutus (didrive) wrote : UdevDb.txt

apport information

Revision history for this message
Destitutus (didrive) wrote : UdevLog.txt

apport information

Revision history for this message
Destitutus (didrive) wrote : WifiSyslog.txt

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.7-rc1 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc1-yakkety/

Changed in linux (Ubuntu):
importance: Undecided → High
tags: added: kernel-da-key xenial
removed: trusty
Changed in linux (Ubuntu Xenial):
status: New → Incomplete
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Changed in linux (Ubuntu Xenial):
importance: Undecided → High
Revision history for this message
Destitutus (didrive) wrote :

4.7.0-040700rc2-generic #201606051831 SMP Sun Jun 5 22:33:44 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Kernel is still affected but behaviour a bit different - kernel crashed immediately after mount

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Changed in linux (Ubuntu Xenial):
status: Incomplete → Confirmed
tags: added: kernel-bug-exists-upstream
Dragan S. (dragan-s)
Changed in linux (Ubuntu Xenial):
assignee: nobody → Dragan S. (dragan-s)
Revision history for this message
Dragan S. (dragan-s) wrote :

I can reproduce this problem and I have pinpointed the problem. Working on creating a patch and a test build.

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

Other bug subscribers

Remote bug watches

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