selftests/bpf: use canonical ftrace path
authorRoss Zwisler <zwisler@google.com>
Mon, 13 Mar 2023 20:56:28 +0000 (14:56 -0600)
committerAlexei Starovoitov <ast@kernel.org>
Tue, 14 Mar 2023 04:51:30 +0000 (21:51 -0700)
commitab4c15feb2ebcf9f4abe31457d7cbc8f3de9c2ab
treed66282c6c7ff3afb5242d46dfb45925ec17d206f
parent27d7fdf06fdb84455ff585b58c8034e2fab42583
selftests/bpf: use canonical ftrace path

The canonical location for the tracefs filesystem is at
/sys/kernel/tracing.

But, from Documentation/trace/ftrace.rst:

  Before 4.1, all ftrace tracing control files were within the debugfs
  file system, which is typically located at /sys/kernel/debug/tracing.
  For backward compatibility, when mounting the debugfs file system,
  the tracefs file system will be automatically mounted at:

  /sys/kernel/debug/tracing

Many tests in the bpf selftest code still refer to this older debugfs
path, so let's update them to avoid confusion.

Signed-off-by: Ross Zwisler <zwisler@google.com>
Acked-by: Michael S. Tsirkin <mst@redhat.com>
Reviewed-by: Steven Rostedt (Google) <rostedt@goodmis.org>
Link: https://lore.kernel.org/r/20230313205628.1058720-3-zwisler@kernel.org
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
tools/testing/selftests/bpf/get_cgroup_id_user.c
tools/testing/selftests/bpf/prog_tests/kprobe_multi_test.c
tools/testing/selftests/bpf/prog_tests/task_fd_query_tp.c
tools/testing/selftests/bpf/prog_tests/tp_attach_query.c
tools/testing/selftests/bpf/prog_tests/trace_printk.c
tools/testing/selftests/bpf/prog_tests/trace_vprintk.c
tools/testing/selftests/bpf/progs/test_stacktrace_map.c
tools/testing/selftests/bpf/progs/test_tracepoint.c
tools/testing/selftests/bpf/test_ftrace.sh
tools/testing/selftests/bpf/test_tunnel.sh
tools/testing/selftests/bpf/trace_helpers.c