Searched refs:follow_link (Results 1 – 6 of 6) sorted by relevance
233 had ->revalidate()) add calls in ->follow_link()/->readlink().539 from ->follow_link for normal symlinks, or nd_jump_link for magic592 symlink body is and use simple_follow_link() as ->follow_link().598 calling conventions for ->follow_link() have changed. Instead of returning629 ->follow_link() is replaced with ->get_link(); same API, except that
1064 The place for all this to happen is the ``i_op->follow_link()`` inode1070 looked at previously, ``->follow_link()`` would need to be careful that1073 reference with ``->follow_link()`` is not yet done in RCU-walk mode, the1178 one of these, the ``->follow_link()`` method in "procfs" doesn't return1180 ``nameidata`` in place to point to that target. ``->follow_link()`` then
69 use the follow_link inode operation to trigger the mount.
140 static char *follow_link(char *link) in follow_link() function940 char *name = follow_link(host_root_path); in hostfs_fill_sb_common()
108 2) follow_link and readdir code does not follow dfs junctions
474 static int follow_link(struct pcmcia_socket *s, tuple_t *tuple) in follow_link() function552 ofs = follow_link(s, tuple); in pccard_get_next_tuple()