vfs: document locking requirements for d_move, __d_move and d_materialise_unique
authorJeff Layton <jlayton@redhat.com>
Tue, 26 Jul 2011 17:33:16 +0000 (13:33 -0400)
committerAl Viro <viro@zeniv.linux.org.uk>
Tue, 26 Jul 2011 17:41:14 +0000 (13:41 -0400)
commitc46c887744b330795eba55fdb96343c36d481765
tree3e4608981b87d8b5d2b23827988312d7c35778b2
parent41c96486f238e6a545f52215f95fe69748abf603
vfs: document locking requirements for d_move, __d_move and d_materialise_unique

Adding a comment to d_materialise_unique per Al's request...

d_move and __d_move have some pretty substantial locking requirements,
but they are not clearly documented. Add some comments spelling them
out. Also, document the requirement for the i_mutex of the parent in
d_materialise_unique.

Cc: Al Viro <viro@ZenIV.linux.org.uk>
Signed-off-by: Jeff Layton <jlayton@redhat.com>
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
fs/dcache.c