linux-kernel - Re: [BUGFIX PATCH 3/3] selftests/ftrace: Do not to use absolute debugfs path

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20191124164212.50029da6@oasis.local.home>
Date:   Sun, 24 Nov 2019 16:42:12 -0500
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Masami Hiramatsu <mhiramat@...nel.org>
Cc:     Shuah Khan <shuah@...nel.org>, linux-kselftest@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [BUGFIX PATCH 3/3] selftests/ftrace: Do not to use absolute
 debugfs path

On Sun, 24 Nov 2019 13:55:57 +0900
Masami Hiramatsu <mhiramat@...nel.org> wrote:

> Use relative path to trigger file instead of absolute debugfs path,
> because if the user uses tracefs instead of debugfs, it can be
> mounted at /sys/kernel/tracing.
> Anyway, since the ftracetest is designed to be run at the tracing
> directory, user doesn't need to use absolute path.
> 
> Signed-off-by: Masami Hiramatsu <mhiramat@...nel.org>
>

Reviewed-by: Steven Rostedt (VMware) <rostedt@...dmis.org>

-- Steve