diff options
author | Masami Hiramatsu <mhiramat@kernel.org> | 2021-08-19 19:26:02 +0900 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2021-09-22 12:28:00 +0200 |
commit | 3aedfe4b080026157a36bf2be6495e158c7d0c62 (patch) | |
tree | 21207867a6bdca045e77d54f4b58250d7d2bbafe /drivers/pci | |
parent | 75420f9400a6792dc4b43e5a43ee0f105dd3f9ee (diff) | |
download | kernel_replicant_linux-3aedfe4b080026157a36bf2be6495e158c7d0c62.tar.gz kernel_replicant_linux-3aedfe4b080026157a36bf2be6495e158c7d0c62.tar.bz2 kernel_replicant_linux-3aedfe4b080026157a36bf2be6495e158c7d0c62.zip |
tracing/probes: Reject events which have the same name of existing one
[ Upstream commit 8e242060c6a4947e8ae7d29794af6a581db08841 ]
Since kprobe_events and uprobe_events only check whether the
other same-type probe event has the same name or not, if the
user gives the same name of the existing tracepoint event (or
the other type of probe events), it silently fails to create
the tracefs entry (but registered.) as below.
/sys/kernel/tracing # ls events/task/task_rename
enable filter format hist id trigger
/sys/kernel/tracing # echo p:task/task_rename vfs_read >> kprobe_events
[ 113.048508] Could not create tracefs 'task_rename' directory
/sys/kernel/tracing # cat kprobe_events
p:task/task_rename vfs_read
To fix this issue, check whether the existing events have the
same name or not in trace_probe_register_event_call(). If exists,
it rejects to register the new event.
Link: https://lkml.kernel.org/r/162936876189.187130.17558311387542061930.stgit@devnote2
Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'drivers/pci')
0 files changed, 0 insertions, 0 deletions