diff options
| author | Michael Vetter <[email protected]> | 2024-10-17 20:01:32 +0000 |
|---|---|---|
| committer | Petr Mladek <[email protected]> | 2024-10-22 15:13:11 +0000 |
| commit | 62597edf6340191511bdf9a7f64fa315ddc58805 (patch) | |
| tree | 823af88954dcf55492e8aa424db6b29e5dfc466a /drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c | |
| parent | selftests: livepatch: save and restore kprobe state (diff) | |
| download | kernel-62597edf6340191511bdf9a7f64fa315ddc58805.tar.gz kernel-62597edf6340191511bdf9a7f64fa315ddc58805.zip | |
selftests: livepatch: test livepatching a kprobed function
The test proves that a function that is being kprobed and uses a
post_handler cannot be livepatched.
Only one ftrace_ops with FTRACE_OPS_FL_IPMODIFY set may be registered
to any given function at a time.
Note that the conflicting kprobe could not be created using the
tracefs interface, see Documentation/trace/kprobetrace.rst.
This interface uses only the pre_handler(), see alloc_trace_kprobe().
But FTRACE_OPS_FL_IPMODIFY is used only when the kprobe is using a
post_handler, see arm_kprobe_ftrace().
Signed-off-by: Michael Vetter <[email protected]>
Reviewed-by: Miroslav Benes <[email protected]>
Reviewed-by: Joe Lawrence <[email protected]>
Tested-by: Marcos Paulo de Souza <[email protected]>
Reviewed-by: Marcos Paulo de Souza <[email protected]>
Reviewed-by: Petr Mladek <[email protected]>
Tested-by: Petr Mladek <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Petr Mladek <[email protected]>
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c')
0 files changed, 0 insertions, 0 deletions
