kernel/rcu/rcutorture.c
Source file repositories/reference/linux-study-clean/kernel/rcu/rcutorture.c
File Facts
- System
- Linux kernel
- Corpus path
kernel/rcu/rcutorture.c- Extension
.c- Size
- 155400 bytes
- Lines
- 4793
- Domain
- Core OS
- Bucket
- Scheduler, Processes, Timers, Sync, And Syscalls
- 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.
- 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/types.hlinux/kernel.hlinux/init.hlinux/module.hlinux/kthread.hlinux/err.hlinux/spinlock.hlinux/smp.hlinux/rcupdate_wait.hlinux/rcu_notifier.hlinux/interrupt.hlinux/sched/signal.huapi/linux/sched/types.hlinux/atomic.hlinux/bitops.hlinux/completion.hlinux/moduleparam.hlinux/percpu.hlinux/notifier.hlinux/reboot.hlinux/freezer.hlinux/cpu.hlinux/delay.hlinux/stat.hlinux/srcu.hlinux/slab.hlinux/trace_clock.hasm/byteorder.hlinux/torture.hlinux/vmalloc.hlinux/sched/debug.hlinux/sched/sysctl.h
Detected Declarations
struct rcu_torture_reader_checkstruct rcu_torturestruct rt_read_segstruct rcu_torture_opsstruct rcu_torture_one_read_statestruct rcu_torture_one_read_state_updownstruct fwd_cb_statestruct rcu_fwd_cbstruct rcu_launder_histstruct rcu_fwdfunction rcu_trace_clock_localfunction rcu_trace_clock_localfunction shutdown_time_arrivedfunction rcu_torture_allocfunction rcu_torture_freefunction torture_readlock_not_heldfunction rcu_torture_read_lockfunction rcu_read_delayfunction rcu_torture_read_unlockfunction rcu_torture_readlock_nestingfunction rcu_torture_pipe_update_onefunction rcu_torture_pipe_updatefunction rcu_torture_cbfunction rcu_no_completedfunction rcu_torture_deferred_freefunction rcu_sync_torture_initfunction rcu_poll_need_2gpfunction rcu_busted_torture_deferred_freefunction synchronize_rcu_bustedfunction srcu_torture_initfunction srcu_get_gp_datafunction srcu_torture_read_lockfunction srcu_read_delayfunction srcu_torture_read_unlockfunction torture_srcu_read_lock_heldfunction srcu_torture_have_up_downfunction srcu_torture_down_readfunction srcu_torture_up_readfunction srcu_torture_completedfunction srcu_torture_deferred_freefunction srcu_torture_synchronizefunction srcu_torture_get_gp_statefunction srcu_torture_start_gp_pollfunction srcu_torture_poll_gp_statefunction srcu_torture_callfunction srcu_torture_barrierfunction srcu_torture_statsfunction srcu_torture_synchronize_expedited
Annotated Snippet
module_init(rcu_torture_init);
module_exit(rcu_torture_cleanup);
Annotation
- Immediate include surface: `linux/types.h`, `linux/kernel.h`, `linux/init.h`, `linux/module.h`, `linux/kthread.h`, `linux/err.h`, `linux/spinlock.h`, `linux/smp.h`.
- Detected declarations: `struct rcu_torture_reader_check`, `struct rcu_torture`, `struct rt_read_seg`, `struct rcu_torture_ops`, `struct rcu_torture_one_read_state`, `struct rcu_torture_one_read_state_updown`, `struct fwd_cb_state`, `struct rcu_fwd_cb`, `struct rcu_launder_hist`, `struct rcu_fwd`.
- Atlas domain: Core OS / Scheduler, Processes, Timers, Sync, And Syscalls.
- 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.