https://bugzilla.kernel.org/show_bug.cgi?id=200981 Dave Chinner (david@xxxxxxxxxxxxx) changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |david@xxxxxxxxxxxxx --- Comment #4 from Dave Chinner (david@xxxxxxxxxxxxx) --- Ok, so the obvious fix doesn't help. Any idea why lockdep is not giving you the full stack trace of where the lock that was leaked to userspace was first accessed? Without that, we have no idea which of the 70-odd calls to xfs_trans_alloc() in the XFS code the lockdep warning refers to. At minimum, we need to know what syscall is triggering the warning so we know what code to look at. Also, can you reproduce this on older kernels? If not, could you bisect it? -Dave. -- You are receiving this mail because: You are watching the assignee of the bug.
