include/linux/pidfs.h
Source file repositories/reference/linux-study-clean/include/linux/pidfs.h
File Facts
- System
- Linux kernel
- Corpus path
include/linux/pidfs.h- Extension
.h- Size
- 979 bytes
- Lines
- 37
- 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
linux/gfp_types.h
Detected Declarations
struct coredump_paramsfunction pidfs_register_pid
Annotated Snippet
#ifndef _LINUX_PID_FS_H
#define _LINUX_PID_FS_H
#include <linux/gfp_types.h>
struct coredump_params;
struct file *pidfs_alloc_file(struct pid *pid, unsigned int flags);
void __init pidfs_init(void);
void pidfs_prepare_pid(struct pid *pid);
int pidfs_add_pid(struct pid *pid);
void pidfs_remove_pid(struct pid *pid);
void pidfs_exit(struct task_struct *tsk);
#ifdef CONFIG_COREDUMP
void pidfs_coredump(const struct coredump_params *cprm);
#endif
extern const struct dentry_operations pidfs_dentry_operations;
int pidfs_register_pid_gfp(struct pid *pid, gfp_t gfp);
/**
* pidfs_register_pid - register a struct pid in pidfs
* @pid: pid to pin
*
* Register a struct pid in pidfs.
*
* Return: On success zero, on error a negative error code is returned.
*/
static inline int pidfs_register_pid(struct pid *pid)
{
return pidfs_register_pid_gfp(pid, GFP_KERNEL);
}
void pidfs_free_pid(struct pid *pid);
#endif /* _LINUX_PID_FS_H */
Annotation
- Immediate include surface: `linux/gfp_types.h`.
- Detected declarations: `struct coredump_params`, `function pidfs_register_pid`.
- 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.