aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/filesystems/path-lookup.txt
diff options
context:
space:
mode:
authorNick Piggin <npiggin@kernel.dk>2011-01-07 01:49:57 -0500
committerNick Piggin <npiggin@kernel.dk>2011-01-07 01:50:29 -0500
commit34286d6662308d82aed891852d04c7c3a2649b16 (patch)
treec4b7311404d302e7cb94df7a4690298e1059910a /Documentation/filesystems/path-lookup.txt
parent44a7d7a878c9cbb74f236ea755b25b6b2e26a9a9 (diff)
fs: rcu-walk aware d_revalidate method
Require filesystems be aware of .d_revalidate being called in rcu-walk mode (nd->flags & LOOKUP_RCU). For now do a simple push down, returning -ECHILD from all implementations. Signed-off-by: Nick Piggin <npiggin@kernel.dk>
Diffstat (limited to 'Documentation/filesystems/path-lookup.txt')
-rw-r--r--Documentation/filesystems/path-lookup.txt5
1 files changed, 2 insertions, 3 deletions
diff --git a/Documentation/filesystems/path-lookup.txt b/Documentation/filesystems/path-lookup.txt
index 09b2878724a1..8789d1810bed 100644
--- a/Documentation/filesystems/path-lookup.txt
+++ b/Documentation/filesystems/path-lookup.txt
@@ -317,11 +317,10 @@ The detailed design for rcu-walk is like this:
317The cases where rcu-walk cannot continue are: 317The cases where rcu-walk cannot continue are:
318* NULL dentry (ie. any uncached path element) 318* NULL dentry (ie. any uncached path element)
319* parent with d_inode->i_op->permission or ACLs 319* parent with d_inode->i_op->permission or ACLs
320* dentries with d_revalidate
321* Following links 320* Following links
322 321
323In future patches, permission checks and d_revalidate become rcu-walk aware. It 322In future patches, permission checks become rcu-walk aware. It may be possible
324may be possible eventually to make following links rcu-walk aware. 323eventually to make following links rcu-walk aware.
325 324
326Uncached path elements will always require dropping to ref-walk mode, at the 325Uncached path elements will always require dropping to ref-walk mode, at the
327very least because i_mutex needs to be grabbed, and objects allocated. 326very least because i_mutex needs to be grabbed, and objects allocated.