fs/notify/dnotify/dnotify.c
Source file repositories/reference/linux-study-clean/fs/notify/dnotify/dnotify.c
File Facts
- System
- Linux kernel
- Corpus path
fs/notify/dnotify/dnotify.c- Extension
.c- Size
- 11298 bytes
- Lines
- 414
- Domain
- Core OS
- Bucket
- VFS And Filesystem Core
- Inferred role
- Core OS: exported/initcall integration point
- Status
- integration 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.
- Exports symbols or registers init work; inspect boot/module ordering and who consumes the exported contract.
- Uses kernel synchronization; read lock ordering, sleepability, and interrupt context assumptions before translating.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/fs.hlinux/module.hlinux/sched.hlinux/sched/signal.hlinux/dnotify.hlinux/init.hlinux/security.hlinux/spinlock.hlinux/slab.hlinux/fsnotify_backend.h
Detected Declarations
struct dnotify_markfunction dnotify_sysctl_initfunction dnotify_recalc_inode_maskfunction dnotify_handle_eventfunction dnotify_free_markfunction dnotify_flushfunction convert_argfunction attach_dnfunction fcntl_dirnotifyfunction dnotify_initmodule init dnotify_init
Annotated Snippet
module_init(dnotify_init)Annotation
- Immediate include surface: `linux/fs.h`, `linux/module.h`, `linux/sched.h`, `linux/sched/signal.h`, `linux/dnotify.h`, `linux/init.h`, `linux/security.h`, `linux/spinlock.h`.
- Detected declarations: `struct dnotify_mark`, `function dnotify_sysctl_init`, `function dnotify_recalc_inode_mask`, `function dnotify_handle_event`, `function dnotify_free_mark`, `function dnotify_flush`, `function convert_arg`, `function attach_dn`, `function fcntl_dirnotify`, `function dnotify_init`.
- Atlas domain: Core OS / VFS And Filesystem Core.
- Implementation status: integration implementation candidate.
- Synchronization appears in or near this file; preserve lock ordering, sleepability, and interrupt-context constraints.
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.