kernel/time/namespace_internal.h

File Facts

System

Linux kernel

Corpus path

kernel/time/namespace_internal.h

Extension

.h

Size

728 bytes

Lines

29

Domain

Core OS

Bucket

Scheduler, Processes, Timers, Sync, And Syscalls

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.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/mutex.h

Detected Declarations

• struct time_namespace
• function timens_vdso_alloc_vvar_page
• function timens_vdso_free_vvar_page

Annotated Snippet

#ifndef _TIME_NAMESPACE_INTERNAL_H
#define _TIME_NAMESPACE_INTERNAL_H

#include <linux/mutex.h>

struct time_namespace;

/*
 * Protects possibly multiple offsets writers racing each other
 * and tasks entering the namespace.
 */
extern struct mutex timens_offset_lock;

#ifdef CONFIG_TIME_NS_VDSO
int timens_vdso_alloc_vvar_page(struct time_namespace *ns);
void timens_vdso_free_vvar_page(struct time_namespace *ns);
#else /* !CONFIG_TIME_NS_VDSO */
static inline int timens_vdso_alloc_vvar_page(struct time_namespace *ns)
{
	return 0;
}
static inline void timens_vdso_free_vvar_page(struct time_namespace *ns)
{
}
#endif /* CONFIG_TIME_NS_VDSO */

#endif /* _TIME_NAMESPACE_INTERNAL_H */

Annotation

• Immediate include surface: `linux/mutex.h`.
• Detected declarations: `struct time_namespace`, `function timens_vdso_alloc_vvar_page`, `function timens_vdso_free_vvar_page`.
• Atlas domain: Core OS / Scheduler, Processes, Timers, Sync, And Syscalls.
• 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.