kernel/trace/trace_fprobe.c

File Facts

System

Linux kernel

Corpus path

kernel/trace/trace_fprobe.c

Extension

.c

Size

40479 bytes

Lines

1590

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/fprobe.h
• linux/list.h
• linux/module.h
• linux/mutex.h
• linux/rculist.h
• linux/security.h
• linux/tracepoint.h
• linux/uaccess.h
• asm/ptrace.h
• trace_dynevent.h
• trace_probe.h
• trace_probe_kernel.h
• trace_probe_tmpl.h

Detected Declarations

• struct tracepoint_user
• struct trace_fprobe
• struct __find_tracepoint_cb_data
• function tracepoint_user_register
• function tracepoint_user_unregister
• function tracepoint_user_ip
• function __tracepoint_user_free
• function NULL
• function tracepoint_user_put
• function is_trace_fprobe
• function trace_fprobe_is_tracepoint
• function trace_fprobe_is_busy
• function trace_fprobe_match_command_head
• function trace_fprobe_match
• function trace_fprobe_is_registered
• function process_fetch_insn
• function __fentry_trace_func
• function fentry_trace_func
• function store_fprobe_entry_data
• function trace_fprobe_entry_handler
• function __fexit_trace_func
• function fexit_trace_func
• function fentry_perf_func
• function fexit_perf_func
• function fentry_dispatcher
• function fexit_dispatcher
• function free_trace_fprobe
• function it
• function print_fentry_event
• function print_fexit_event
• function fentry_event_define_fields
• function fexit_event_define_fields
• function init_trace_event_call
• function register_fprobe_event
• function unregister_fprobe_event
• function __regsiter_tracepoint_fprobe
• function trace_fprobe_verify_target
• function __register_trace_fprobe
• function __unregister_trace_fprobe
• function unregister_trace_fprobe
• function trace_fprobe_has_same_fprobe
• function list_for_each_entry
• function append_trace_fprobe_event
• function register_trace_fprobe_event
• function __find_tracepoint_module_cb
• function __find_tracepoint_cb
• function tracepoint_user_within_module
• function tracepoint_user_register_again

Annotated Snippet

core_initcall(init_fprobe_trace_early);

Annotation

• Immediate include surface: `linux/fprobe.h`, `linux/list.h`, `linux/module.h`, `linux/mutex.h`, `linux/rculist.h`, `linux/security.h`, `linux/tracepoint.h`, `linux/uaccess.h`.
• Detected declarations: `struct tracepoint_user`, `struct trace_fprobe`, `struct __find_tracepoint_cb_data`, `function tracepoint_user_register`, `function tracepoint_user_unregister`, `function tracepoint_user_ip`, `function __tracepoint_user_free`, `function NULL`, `function tracepoint_user_put`, `function is_trace_fprobe`.
• 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.