fs/netfs/read_pgpriv2.c

File Facts

System

Linux kernel

Corpus path

fs/netfs/read_pgpriv2.c

Extension

.c

Size

6280 bytes

Lines

233

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/export.h
• linux/fs.h
• linux/mm.h
• linux/pagemap.h
• linux/slab.h
• linux/task_io_accounting_ops.h
• internal.h

Detected Declarations

• function Copyright
• function netfs_pgpriv2_copy_to_cache
• function netfs_pgpriv2_end_copy_to_cache
• function netfs_pgpriv2_unlock_copied_folios

Annotated Snippet

if (slot >= folioq_nr_slots(folioq)) {
			folioq = rolling_buffer_delete_spent(&creq->buffer);
			if (!folioq)
				goto done;
			slot = 0;
		}

		if (fpos + fsize >= collected_to)
			break;
	}

	creq->buffer.tail = folioq;
done:
	creq->buffer.first_tail_slot = slot;
	return made_progress;
}

Annotation

• Immediate include surface: `linux/export.h`, `linux/fs.h`, `linux/mm.h`, `linux/pagemap.h`, `linux/slab.h`, `linux/task_io_accounting_ops.h`, `internal.h`.
• Detected declarations: `function Copyright`, `function netfs_pgpriv2_copy_to_cache`, `function netfs_pgpriv2_end_copy_to_cache`, `function netfs_pgpriv2_unlock_copied_folios`.
• 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.