hfsplus Kernel module crashes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
After some weeks of a mounted USB mass storage device, the hfsplus Kernel module crashes, leaving the file system half-mounted, but not unmountable, as there were processes in the mounted directory tree.
I don't know if the root cause was a bug in updatedb, but a kernel module should never crash on userland process investigation.
I don't think the file system was perfectly clear:
[1700207.162684] hfs: inconsistency in B*Tree (1,0,1,0,2620)
But the crash is quite a few times later:
Here's the stack trace:
[1785597.415062] Modules linked in: nls_utf8 btrfs zlib_deflate libcrc32c ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs xfs reiserfs usb_storage uas bnep rfcomm bluetooth pci_stub vboxpci vboxnetadp vboxnetflt vboxdrv parport_pc ppdev binfmt_misc joydev snd_hda_
[1785597.415257]
[1785597.415263] Pid: 21313, comm: updatedb.mlocat Tainted: G C 3.0.0-17-generic #30-Ubuntu Dell Inc. OptiPlex 790/0HY9JP
[1785597.415297] RIP: 0010:[<
[1785597.415322] RSP: 0018:ffff8800c6
[1785597.415337] RAX: ffff8800c6a8f826 RBX: ffff8800c6a8f826 RCX: 0000000000000002
[1785597.415357] RDX: 0000000000000002 RSI: db73880000000639 RDI: ffff8800c6a8f826
[1785597.415376] RBP: ffff8800c6a8f808 R08: 0000000000000011 R09: 6db6db6db6db6db7
[1785597.415395] R10: ffff880000000000 R11: 0000000000000003 R12: 0000000000000002
[1785597.415414] R13: 0000000000000002 R14: 0000000000000002 R15: ffff880030ef9540
[1785597.415434] FS: 00007fc0f336672
[1785597.415455] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[1785597.415471] CR2: 00007fc0f3362000 CR3: 000000007dc65000 CR4: 00000000000426e0
[1785597.415490] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[1785597.415510] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[1785597.415529] Process updatedb.mlocat (pid: 21313, threadinfo ffff8800c6a8e000, task ffff880002ce4560)
[1785597.415553] Stack:
[1785597.415559] ffffffffa06e3941 ffff8800c6a8f818 ffff880000000000 6db6db6db6db6db7
[1785597.415583] 0000160000000000 0000000000000011 0000000000000000 000000000000000b
[1785597.415607] ffff880030ef9540 ffff880030ef9540 ffff8800c6a8f970 00000000000000e3
[1785597.415637] Call Trace:
[1785597.415652] [<ffffffffa06e3
[1785597.415672] [<ffffffffa06e3
[1785597.415692] [<ffffffffa06e5
[1785597.415712] [<ffffffffa06e6
[1785597.415732] [<ffffffffa06e6
[1785597.415751] [<ffffffffa06e6
[1785597.415770] [<ffffffffa06e2
[1785597.415790] [<ffffffff81153
[1785597.415807] [<ffffffff81246
[1785597.416769] [<ffffffff81199
[1785597.417940] [<ffffffff81222
[1785597.418989] [<ffffffff8120b
[1785597.419918] [<ffffffff81246
[1785597.420844] [<ffffffffa07c9
[1785597.421765] [<ffffffff81153
[1785597.422681] [<ffffffff8117d
[1785597.423584] [<ffffffff81172
[1785597.424644] [<ffffffff81180
[1785597.425888] [<ffffffff81175
[1785597.426969] [<ffffffff81176
[1785597.427861] [<ffffffff8110c
[1785597.428752] [<ffffffff812f6
[1785597.429643] [<ffffffff81177
[1785597.430531] [<ffffffff81177
[1785597.431432] [<ffffffff812b8
[1785597.432381] [<ffffffff815f2
[1785597.433282] [<ffffffff8116c
[1785597.434185] [<ffffffff81177
[1785597.435093] [<ffffffff8116c
[1785597.435990] [<ffffffff8116d
[1785597.436874] [<ffffffff8116d
[1785597.437854] [<ffffffff815fb
[1785597.438826] Code: 43 4e 48 83 c4 08 5b 5d c3 66 90 e8 fb fd ff ff eb e6 90 90 90 90 90 90 90 90 90 48 89 f8 89 d1 c1 e9 03 83 e2 07 f3 48 a5 89 d1 <f3> a4 c3 20 48 83 ea 20 4c 8b 06 4c 8b 4e 08 4c 8b 56 10 4c 8b
[1785597.440740] RIP [<ffffffff812f5
[1785597.441663] RSP <ffff8800c6a8f7a0>
[1785597.481628] ---[ end trace bb844955408b4d84 ]---
My system:
root@kathy:~# uname -a
Linux kathy 3.0.0-17-generic #30-Ubuntu SMP Thu Mar 8 20:45:39 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1027887
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.