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
839 automount point is found, or in a couple of cases involving symlinks.
937 A walk among the symlinks
943 symlinks and lead to the special care needed for the final component.
951 appear in a path prior to the final component: directories and symlinks.
974 There are two reasons for placing limits on how many symlinks can
995 at most 40 (MAXSYMLINKS) symlinks in any one path lookup.  It previously imposed
1002 symlinks.  In many cases this will be sufficient.  If it isn't, a
1003 separate stack is allocated with room for 40 symlinks.  Pathname
1011 Storage and lifetime of cached symlinks
1015 entries, symlinks are cached by Linux to avoid repeated costly access
1022 While each filesystem is free to make its own choice, symlinks are
1023 typically stored in one of two places.  Short symlinks are often
1040 sufficient for accessing some cached symlinks safely.  In these cases,
1048 a page will not disappear.  So for these symlinks the pathname lookup
1099 components in the path and all of the non-final symlinks.  As symlinks
1137 A pair of special-case symlinks deserve a little further explanation.
1141 The more obvious case is a symlink to "``/``".  All symlinks starting
1148 The other case involves things in ``/proc`` that look like symlinks but
1177 successive symlinks until one is found that doesn't point to another
1230 "footprints" can be needed when handling symlinks as a counted
1265 being changed (and symlinks never change once created).  Even without
1324 relates to restricting the following of trailing symlinks.
1364 symlinks.  Some system calls set or clear it implicitly, while
1388 symlinks that are stored in the inode so, while it handles many ext4
1389 symlinks, it doesn't help with NFS, XFS, or Btrfs.  That support