Searched refs:d_manage (Results 1 – 7 of 7) sorted by relevance
| /Linux-v5.10/Documentation/filesystems/ |
| D | autofs.rst | 117 related behaviours are invoked, both using the `d_op->d_manage()`
121 directory, d_manage() will be called with the `rcu_walk` parameter set
147 first. This means that d_manage cannot *always* return -EISDIR for
151 `d_manage` also returns `-EISDIR` if the dentry shouldn't be a
178 `->d_manage()` with `rcu_walk` set to `true`.
180 In this case `d_manage()` must avoid blocking and should avoid taking
186 In the `rcu_walk` case, `d_manage()` cannot return -EISDIR to tell the
189 mounted, it *will* fall back to REF-walk. `d_manage()` cannot make the
193 So `d_manage()`, when called with `rcu_walk` set, should either return
297 `d_manage` will block until the daemon affirms that the unmount has
|
| D | locking.rst | 31 int (*d_manage)(const struct path *, bool);
50 d_manage: no no yes (ref-walk) maybe
|
| D | path-lookup.rst | 547 ``d_manage()`` dentry operation be called before handling any possible
551 unmounted, the ``d_manage()`` function will usually wait for that
560 ``d_manage()`` by returning ``-EISDIR``.
570 If this flag is set, and ``d_manage()`` didn't return ``-EISDIR``,
578 If ``d_manage()`` allowed us to get this far, and ``lookup_mnt()`` didn't
|
| D | vfs.rst | 1165 int (*d_manage)(const struct path *, bool);
1300 ``d_manage``
|
| /Linux-v5.10/include/linux/ |
| D | dcache.h | 148 int (*d_manage)(const struct path *, bool); member
|
| /Linux-v5.10/fs/autofs/ |
| D | root.c | 59 .d_manage = autofs_d_manage,
|
| /Linux-v5.10/fs/ |
| D | namei.c | 1218 ret = path->dentry->d_op->d_manage(path, false); in __traverse_mounts()
1330 int res = dentry->d_op->d_manage(path, true); in __follow_mount_rcu()
|
