lkml.org 
[lkml]   [2012]   [Jun]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: processes hung after sys_renameat, and 'missing' processes

> Also, sysrq-w is usually way more interesting than 't' when there are
> processes stuck on a mutex.
>
> Because yes, it looks like you have a boattload of trinity processes
> stuck on an inode mutex. Looks like every single one of them is in
> 'lock_rename()'. It *shouldn't* be an ABBA deadlock, since lockdep
> should have noticed that, but who knows.

lock_rename() is a bit of a red herring here - they appear to be all
within-directory renames, so it's just a "trying to rename something
in a directory that has ->i_mutex held by something else".

IOW, something else in there is holding ->i_mutex - something that
either hadn't been through lock_rename() at all or has already
passed through it and still hadn't got around to unlock_rename().
In either case, suspects won't have lock_rename() in the trace...


\
 
 \ /
  Last update: 2012-06-04 01:41    [W:1.733 / U:0.264 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site