fs/nfs/symlink.c
Source file repositories/reference/linux-study-clean/fs/nfs/symlink.c
File Facts
- System
- Linux kernel
- Corpus path
fs/nfs/symlink.c- Extension
.c- Size
- 1875 bytes
- Lines
- 81
- Domain
- Core OS
- Bucket
- VFS And Filesystem Core
- Inferred role
- Core OS: implementation source
- Status
- source implementation candidate
Why This File Exists
Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
- Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
- Allocates kernel memory; connect allocation flags and lifetime to context constraints.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/time.hlinux/errno.hlinux/sunrpc/clnt.hlinux/nfs.hlinux/nfs2.hlinux/nfs_fs.hlinux/pagemap.hlinux/stat.hlinux/mm.hlinux/string.hinternal.h
Detected Declarations
function Copyright
Annotated Snippet
if (!folio_test_uptodate(folio)) {
folio_put(folio);
return ERR_PTR(-ECHILD);
}
} else {
err = ERR_PTR(nfs_revalidate_mapping(inode, inode->i_mapping));
if (err)
return err;
folio = read_cache_folio(&inode->i_data, 0, nfs_symlink_filler,
NULL);
if (IS_ERR(folio))
return ERR_CAST(folio);
}
set_delayed_call(done, page_put_link, folio);
return folio_address(folio);
}
/*
* symlinks can't do much...
*/
const struct inode_operations nfs_symlink_inode_operations = {
.get_link = nfs_get_link,
.getattr = nfs_getattr,
.setattr = nfs_setattr,
.fileattr_get = nfs_fileattr_get,
};
Annotation
- Immediate include surface: `linux/time.h`, `linux/errno.h`, `linux/sunrpc/clnt.h`, `linux/nfs.h`, `linux/nfs2.h`, `linux/nfs_fs.h`, `linux/pagemap.h`, `linux/stat.h`.
- Detected declarations: `function Copyright`.
- Atlas domain: Core OS / VFS And Filesystem Core.
- Implementation status: source implementation candidate.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.