Re: [patch] lockdep: annotate vfs_rmdir for filesystems that take i_mutex in delete_inode
- From: Arjan van de Ven <arjan@xxxxxxxxxxxxxxx>
- Date: Wed, 26 Jul 2006 08:38:28 +0200
On Wed, 2006-07-26 at 08:32 +0200, Arjan van de Ven wrote:
The VFS takes the directory i_mutex and reiserfs_delete_inode() takes the
to-be-deleted file's i_mutex.
That's notabug and lockdep will need to be taught about it.
Actually the annotation is in vfs_rmdir() since that is where the parent
is taken (this may sound odd but the I_MUTEX_* ordering rules require
the parent taking to be annotated rather than the child)
Ignore this; this one is wrong, more later
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- possible recursive locking detected - while running fs operations in loops - 2.6.18-rc2-git5
- From: Jesper Juhl
- Re: possible recursive locking detected - while running fs operations in loops - 2.6.18-rc2-git5
- From: Andrew Morton
- [patch] lockdep: annotate vfs_rmdir for filesystems that take i_mutex in delete_inode
- From: Arjan van de Ven
- possible recursive locking detected - while running fs operations in loops - 2.6.18-rc2-git5
- Prev by Date: Re: [PATCH] lockdep: don't pull in includes when lockdep disabled
- Next by Date: Re: [PATCH 007 of 9] knfsd: Separate out some parts of nfsd_svc, which start nfs servers.
- Previous by thread: [patch] lockdep: annotate vfs_rmdir for filesystems that take i_mutex in delete_inode
- Next by thread: [patch] lockdep: annotate vfs_rmdir for filesystems that take i_mutex in delete_inode
- Index(es):
Relevant Pages
|
