diff options
| author | Masami Hiramatsu (Google) <[email protected]> | 2025-05-10 03:44:41 +0000 |
|---|---|---|
| committer | Masami Hiramatsu (Google) <[email protected]> | 2025-05-13 13:23:34 +0000 |
| commit | fd837de3c9cb1a162c69bc1fb1f438467fe7f2f5 (patch) | |
| tree | 84dd334214942fa29d0db25c9e065b1839e28073 /drivers/gpu/drm/amd/amdgpu/amdgpu_acpi.c | |
| parent | tracing: add missing trace_probe_log_clear for eprobes (diff) | |
| download | kernel-fd837de3c9cb1a162c69bc1fb1f438467fe7f2f5.tar.gz kernel-fd837de3c9cb1a162c69bc1fb1f438467fe7f2f5.zip | |
tracing: probes: Fix a possible race in trace_probe_log APIs
Since the shared trace_probe_log variable can be accessed and
modified via probe event create operation of kprobe_events,
uprobe_events, and dynamic_events, it should be protected.
In the dynamic_events, all operations are serialized by
`dyn_event_ops_mutex`. But kprobe_events and uprobe_events
interfaces are not serialized.
To solve this issue, introduces dyn_event_create(), which runs
create() operation under the mutex, for kprobe_events and
uprobe_events. This also uses lockdep to check the mutex is
held when using trace_probe_log* APIs.
Link: https://lore.kernel.org/all/174684868120.551552.3068655787654268804.stgit@devnote2/
Reported-by: Paul Cacheux <[email protected]>
Closes: https://lore.kernel.org/all/[email protected]/
Fixes: ab105a4fb894 ("tracing: Use tracing error_log with probe events")
Signed-off-by: Masami Hiramatsu (Google) <[email protected]>
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_acpi.c')
0 files changed, 0 insertions, 0 deletions
