aboutsummaryrefslogtreecommitdiffstats
path: root/tools/perf/util/probe-event.c
diff options
context:
space:
mode:
authorRavi Bangoria <ravi.bangoria@linux.ibm.com>2018-08-20 10:12:49 +0530
committerSteven Rostedt (VMware) <rostedt@goodmis.org>2018-09-24 04:44:54 -0400
commitccea8727dc27d8f46df6557f9260ab32760ef409 (patch)
tree2c414868068fa1928f52fd5d295f3e17a5ff1c42 /tools/perf/util/probe-event.c
parentuprobes/sdt: Prevent multiple reference counter for same uprobe (diff)
downloadlinux-dev-ccea8727dc27d8f46df6557f9260ab32760ef409.tar.xz
linux-dev-ccea8727dc27d8f46df6557f9260ab32760ef409.zip
trace_uprobe/sdt: Prevent multiple reference counter for same uprobe
We assume to have only one reference counter for one uprobe. Don't allow user to add multiple trace_uprobe entries having same inode+offset but different reference counter. Ex, # echo "p:sdt_tick/loop2 /home/ravi/tick:0x6e4(0x10036)" > uprobe_events # echo "p:sdt_tick/loop2_1 /home/ravi/tick:0x6e4(0xfffff)" >> uprobe_events bash: echo: write error: Invalid argument # dmesg trace_kprobe: Reference counter offset mismatch. There is one exception though: When user is trying to replace the old entry with the new one, we allow this if the new entry does not conflict with any other existing entries. Link: http://lkml.kernel.org/r/20180820044250.11659-4-ravi.bangoria@linux.ibm.com Acked-by: Srikar Dronamraju <srikar@linux.vnet.ibm.com> Reviewed-by: Song Liu <songliubraving@fb.com> Reviewed-by: Oleg Nesterov <oleg@redhat.com> Tested-by: Song Liu <songliubraving@fb.com> Signed-off-by: Ravi Bangoria <ravi.bangoria@linux.ibm.com> Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Diffstat (limited to 'tools/perf/util/probe-event.c')
0 files changed, 0 insertions, 0 deletions