Bug 92531 - [BISECTED]soft lockup while removing directory trees under 3.2.66
Summary: [BISECTED]soft lockup while removing directory trees under 3.2.66
Status: NEW
Alias: None
Product: File System
Classification: Unclassified
Component: VFS (show other bugs)
Hardware: IA-32 Linux
: P1 normal
Assignee: fs_vfs
Depends on:
Reported: 2015-02-02 18:54 UTC by NUXI
Modified: 2016-03-20 10:14 UTC (History)
3 users (show)

See Also:
Kernel Version: 3.2.66
Regression: No
Bisected commit-id:

soft lockup trace (1.92 KB, text/plain)
2015-02-02 18:54 UTC, NUXI
vfs: Fix vfsmount_lock imbalance in path_init() (825 bytes, patch)
2015-02-16 03:26 UTC, Ben Hutchings
Details | Diff

Description NUXI 2015-02-02 18:54:03 UTC
Created attachment 165621 [details]
soft lockup trace

If you accidently start multiple instance of "rm -rf" on the same large directory tree, the 3.2.x kernels starting with 3.2.64 seem to lockup and die while firing soft lockup warnings on the way down. See attachment for dmesg output from the event.

How hard this is seems to depend on system performance. I ended up bisecting it from an older piece of hardware just to make it easier to reproduce. So the system the backtrace is from is a 32-bit only system with ext3 filesystem on an adaptec raid controller. But I've also seen it on 32-bit systems running on LSI controllers, 32bit systems running under vmware fake LSI controllers, and once on a 64-bit sytems with an adaptec controller. (All of those other systems also ran ext3.)

I bisected it down to this commit:
Comment 1 Ben Hutchings 2015-02-16 03:26:05 UTC
Created attachment 167001 [details]
vfs: Fix vfsmount_lock imbalance in path_init()

Does this patch fix the issue?
Comment 2 NUXI 2015-02-16 21:06:47 UTC
Yes, that seems to fix it. Thanks Ben.

Note You need to log in before you can comment on or make changes to this bug.