Commit 049b3c10 authored by Al Viro's avatar Al Viro

vfs: update documentation on ->i_dentry handling

we used to need to clean it in RCU callback freeing an inode;
in 3.2 that requirement went away.  Unfortunately, it hadn't
been reflected in Documentation/filesystems/porting.
Signed-off-by: default avatarAl Viro <viro@zeniv.linux.org.uk>
parent 7968ce12
...@@ -355,12 +355,10 @@ protects *all* the dcache state of a given dentry. ...@@ -355,12 +355,10 @@ protects *all* the dcache state of a given dentry.
via rcu-walk path walk (basically, if the file can have had a path name in the via rcu-walk path walk (basically, if the file can have had a path name in the
vfs namespace). vfs namespace).
i_dentry and i_rcu share storage in a union, and the vfs expects Even though i_dentry and i_rcu share storage in a union, we will
i_dentry to be reinitialized before it is freed, so an: initialize the former in inode_init_always(), so just leave it alone in
the callback. It used to be necessary to clean it there, but not anymore
INIT_LIST_HEAD(&inode->i_dentry); (starting at 3.2).
must be done in the RCU callback.
-- --
[recommended] [recommended]
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment