include/linux/kobject_ns.h
Source file repositories/reference/linux-study-clean/include/linux/kobject_ns.h
File Facts
- System
- Linux kernel
- Corpus path
include/linux/kobject_ns.h- Extension
.h- Size
- 1922 bytes
- Lines
- 59
- Domain
- Core OS
- Bucket
- Core Kernel Interface
- 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
- No C-style include directives detected by the generator.
Detected Declarations
struct ns_commonstruct sockstruct kobjectstruct kobj_ns_type_operationsenum kobj_ns_type
Annotated Snippet
struct kobj_ns_type_operations {
enum kobj_ns_type type;
bool (*current_may_mount)(void);
struct ns_common *(*grab_current_ns)(void);
const struct ns_common *(*netlink_ns)(struct sock *sk);
const struct ns_common *(*initial_ns)(void);
void (*drop_ns)(struct ns_common *);
};
int kobj_ns_type_register(const struct kobj_ns_type_operations *ops);
int kobj_ns_type_registered(enum kobj_ns_type type);
const struct kobj_ns_type_operations *kobj_child_ns_ops(const struct kobject *parent);
const struct kobj_ns_type_operations *kobj_ns_ops(const struct kobject *kobj);
bool kobj_ns_current_may_mount(enum kobj_ns_type type);
struct ns_common *kobj_ns_grab_current(enum kobj_ns_type type);
void kobj_ns_drop(enum kobj_ns_type type, struct ns_common *ns);
#endif /* _LINUX_KOBJECT_NS_H */
Annotation
- Detected declarations: `struct ns_common`, `struct sock`, `struct kobject`, `struct kobj_ns_type_operations`, `enum kobj_ns_type`.
- Atlas domain: Core OS / Core Kernel Interface.
- 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.