Pathname lookup – The Linux Kernel documentation
The Linux Kernel documentation discusses the storage and lifetime of cached symlinks. It explains how symlinks are typically stored in either the inode or the page cache, and the mechanisms used for safe access to these cached entries. The article also details the complexities involved when symlinks are stored in different locations and the implications for pathname lookup.
- ▪Symlinks are cached by Linux to avoid repeated access to external storage.
- ▪They are typically stored in the inode or the page cache, depending on the filesystem's choice.
- ▪The pathname lookup code must ensure stable references to cached symlinks, especially when they are not stored in the inode.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Kernel |
| Canonical URL | https://docs.kernel.org/filesystems/path-lookup.html |
| Publication time | Mon, 25 May 2026 10:31:03 +0000 |
| Retrieval time | 2026-05-25T10:37:36.650Z |
| Last seen | 2026-05-25T10:37:36.650Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 8vNKv_QWLXaH |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
Storage and lifetime of cached symlinks¶ Like other filesystem resources, such as inodes and directory entries, symlinks are cached by Linux to avoid repeated costly access to external storage. It is particularly important for RCU-walk to be able to find and temporarily hold onto these cached entries, so that it doesn’t need to drop down into REF-walk. While each filesystem is free to make its own choice, symlinks are typically stored in one of two places. Short symlinks are often stored directly in the inode. When a filesystem allocates a struct inode it typically allocates extra space to store private data (a common object-oriented design pattern in the kernel). This will sometimes include space for a symlink.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Kernel.
Discussion
0 commentsMore from Kernel
