Lines Matching refs:symlinks
9 - <https://lwn.net/Articles/650786/> A walk among the symlinks
27 the early parts of the analysis we will divide off symlinks - leaving
28 them until the final part. Well before we get to symlinks we have
840 automount point is found, or in a couple of cases involving symlinks.
938 A walk among the symlinks
944 symlinks and lead to the special care needed for the final component.
952 appear in a path prior to the final component: directories and symlinks.
975 There are two reasons for placing limits on how many symlinks can
996 at most 40 symlinks in any one path lookup. It previously imposed a
1003 symlinks. In many cases this will be sufficient. If it isn't, a
1004 separate stack is allocated with room for 40 symlinks. Pathname
1012 Storage and lifetime of cached symlinks
1016 entries, symlinks are cached by Linux to avoid repeated costly access
1023 While each filesystem is free to make its own choice, symlinks are
1024 typically stored in one of two places. Short symlinks are often
1041 sufficient for accessing some cached symlinks safely. In these cases,
1049 a page will not disappear. So for these symlinks the pathname lookup
1082 RCU-walk back to REF-walk in the middle of processing nested symlinks
1116 components in the path and all of the non-final symlinks. As symlinks
1156 A pair of special-case symlinks deserve a little further explanation.
1160 The more obvious case is a symlink to "``/``". All symlinks starting
1167 The other case involves things in ``/proc`` that look like symlinks but
1197 successive symlinks until one is found that doesn't point to another
1254 "footprints" can be needed when handling symlinks as a counted
1289 being changed (and symlinks never change once created). Even without
1348 relates to restricting the following of trailing symlinks.
1388 symlinks. Some system calls set or clear it implicitly, while
1412 symlinks that are stored in the inode so, while it handles many ext4
1413 symlinks, it doesn't help with NFS, XFS, or Btrfs. That support