fs/squashfs/page_actor.c
Source file repositories/reference/linux-study-clean/fs/squashfs/page_actor.c
File Facts
- System
- Linux kernel
- Corpus path
fs/squashfs/page_actor.c- Extension
.c- Size
- 3653 bytes
- Lines
- 142
- 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/kernel.hlinux/slab.hlinux/pagemap.hsquashfs_fs_sb.hdecompressor.hpage_actor.h
Detected Declarations
function Copyrightfunction cache_finish_pagefunction page_next_indexfunction direct_finish_page
Annotated Snippet
if (actor->tmp_buffer == NULL) {
kfree(actor);
return NULL;
}
} else
actor->tmp_buffer = NULL;
actor->length = length ? : pages * PAGE_SIZE;
actor->page = page;
actor->pages = pages;
actor->next_page = 0;
actor->returned_pages = 0;
actor->next_index = start_index >> PAGE_SHIFT;
actor->pageaddr = NULL;
actor->last_page = NULL;
actor->alloc_buffer = msblk->decompressor->alloc_buffer;
actor->squashfs_first_page = direct_first_page;
actor->squashfs_next_page = direct_next_page;
actor->squashfs_finish_page = direct_finish_page;
return actor;
}
Annotation
- Immediate include surface: `linux/kernel.h`, `linux/slab.h`, `linux/pagemap.h`, `squashfs_fs_sb.h`, `decompressor.h`, `page_actor.h`.
- Detected declarations: `function Copyright`, `function cache_finish_page`, `function page_next_index`, `function direct_finish_page`.
- 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.