From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Shuah Khan <shuah@kernel.org>, Mark Brown <broonie@kernel.org>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [FIX PATCH] selftests: tracing: Fix to unmount tracefs for recovering environment
Date: Tue, 12 Sep 2023 09:54:57 +0900 [thread overview]
Message-ID: <20230912095457.e5b89f84e168ed06072ea3d5@kernel.org> (raw)
In-Reply-To: <20230911130909.6d3054af@gandalf.local.home>
On Mon, 11 Sep 2023 13:09:09 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> On Sat, 9 Sep 2023 18:36:39 +0900
> "Masami Hiramatsu (Google)" <mhiramat@kernel.org> wrote:
>
> > From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> >
> > Fix to unmount the tracefs if the ftracetest mounted it for recovering
> > system environment. If the tracefs is already mounted, this does nothing.
> >
> > Suggested-by: Mark Brown <broonie@kernel.org>
> > Link: https://lore.kernel.org/all/29fce076-746c-4650-8358-b4e0fa215cf7@sirena.org.uk/
> > Fixes: cbd965bde74c ("ftrace/selftests: Return the skip code when tracing directory not configured in kernel")
> > Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> > ---
> > tools/testing/selftests/ftrace/ftracetest | 8 ++++++++
> > 1 file changed, 8 insertions(+)
> >
> > diff --git a/tools/testing/selftests/ftrace/ftracetest b/tools/testing/selftests/ftrace/ftracetest
> > index cb5f18c06593..89c212d82256 100755
> > --- a/tools/testing/selftests/ftrace/ftracetest
> > +++ b/tools/testing/selftests/ftrace/ftracetest
> > @@ -31,6 +31,9 @@ err_ret=1
> > # kselftest skip code is 4
> > err_skip=4
> >
> > +# umount required
> > +UMOUNT_DIR=""
> > +
> > # cgroup RT scheduling prevents chrt commands from succeeding, which
> > # induces failures in test wakeup tests. Disable for the duration of
> > # the tests.
> > @@ -45,6 +48,9 @@ setup() {
> >
> > cleanup() {
> > echo $sched_rt_runtime_orig > $sched_rt_runtime
> > + if [ "${UMOUNT_DIR}" ]; then
>
> Shouldn't the above be:
>
> if [ ! -z "${UNMOUNT_DIR}" ]; then
>
> ?
I think both are good.
What about using '-n' explictly?
[ -n "${UNMOUNT_DIR}" ]
Thanks,
>
> -- Steve
>
> > + umount ${UMOUNT_DIR} ||:
> > + fi
> > }
> >
> > errexit() { # message
> > @@ -160,11 +166,13 @@ if [ -z "$TRACING_DIR" ]; then
> > mount -t tracefs nodev /sys/kernel/tracing ||
> > errexit "Failed to mount /sys/kernel/tracing"
> > TRACING_DIR="/sys/kernel/tracing"
> > + UMOUNT_DIR=${TRACING_DIR}
> > # If debugfs exists, then so does /sys/kernel/debug
> > elif [ -d "/sys/kernel/debug" ]; then
> > mount -t debugfs nodev /sys/kernel/debug ||
> > errexit "Failed to mount /sys/kernel/debug"
> > TRACING_DIR="/sys/kernel/debug/tracing"
> > + UMOUNT_DIR=${TRACING_DIR}
> > else
> > err_ret=$err_skip
> > errexit "debugfs and tracefs are not configured in this kernel"
>
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2023-09-12 2:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-09 9:36 [FIX PATCH] selftests: tracing: Fix to unmount tracefs for recovering environment Masami Hiramatsu (Google)
2023-09-11 17:09 ` Steven Rostedt
2023-09-12 0:54 ` Masami Hiramatsu [this message]
2023-09-12 0:57 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230912095457.e5b89f84e168ed06072ea3d5@kernel.org \
--to=mhiramat@kernel.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox