From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: sashiko-reviews@lists.linux.dev
Cc: sashiko-bot@kernel.org, linux-trace-kernel@vger.kernel.org,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v13 07/12] selftests: tracing: Add a basic testcase for wprobe
Date: Sun, 30 Aug 2026 14:35:32 +0900 [thread overview]
Message-ID: <20260830143532.0c2aee25c656896388e6bab7@kernel.org> (raw)
In-Reply-To: <20260822093638.8E6971F000E9@smtp.kernel.org>
On Sat, 22 Aug 2026 09:36:38 +0000
sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Medium] Unreachable error handling logic due to early exit under 'set -e'.
> --
>
> --- Patch [7]: [PATCH v13 07/12] selftests: tracing: Add a basic testcase for wprobe ---
> commit 6d72a05750c5dfc08de6b03a6fc65e5144b20b9f
> Author: Masami Hiramatsu (Google) <mhiramat@kernel.org>
>
> selftests: tracing: Add a basic testcase for wprobe
>
> Add an add_remove_wprobe.tc testcase for testing wprobe events that
> tests adding and removing operations.
>
> > diff --git a/tools/testing/selftests/ftrace/test.d/dynevent/add_remove_wprobe.tc b/tools/testing/selftests/ftrace/test.d/dynevent/add_remove_wprobe.tc
> > new file mode 100644
> > --- /dev/null
> > +++ b/tools/testing/selftests/ftrace/test.d/dynevent/add_remove_wprobe.tc
> > @@ -0,0 +1,63 @@
> > +#!/bin/sh
> > +# SPDX-License-Identifier: GPL-2.0
> > +# description: Generic dynamic event - add/remove wprobe events
> > +# requires: dynamic_events "w[:[<group>/][<event>]] [r|w|rw]@<addr>[:<len>]":README
> > +
> > +echo 0 > events/enable
> > +echo > dynamic_events
> > +
> > +# Use jiffies as a variable that is frequently written to.
> > +TARGET=jiffies
> > +
> > +echo "w:my_wprobe w@$TARGET" >> dynamic_events
> > +
> > +if ! grep -q my_wprobe dynamic_events; then
> > + echo "Failed to create wprobe event"
> > + exit_fail
> > +fi
>
> [Severity: Medium]
> Since the ftracetest framework runs these scripts with set -e (errexit)
> enabled, will this script exit immediately if the kernel rejects the event
> creation and the echo command fails?
>
> If so, the subsequent diagnostic grep check and exit_fail call wouldn't be
> reached, leading to a silent failure without the intended error message.
This is expected, the later grep checks whether if creation command succeeded
but the event is not shown in the dynamic_events. Different check.
> > +
> > +if [ ! -d events/wprobes/my_wprobe ]; then
> > + echo "Failed to create wprobe event directory"
> > + exit_fail
> > +fi
> > +
> > +echo 1 > events/wprobes/my_wprobe/enable
> > +
> > +# Check if the event is enabled
> > +if ! grep -q 1 events/wprobes/my_wprobe/enable; then
> > + echo "Failed to enable wprobe event"
> > + exit_fail
> > +fi
>
> [Severity: Medium]
> Similarly, if enabling the wprobe fails at the sysfs boundary, would this
> echo cause an early exit and bypass the diagnostic error message here as well?
Also, this is a kind of double check. Even if writing 1 to enable
succeeded, it is failed to set internal flag. This checks such problem.
>
> [ ... ]
>
> > +echo "-:my_wprobe" >> dynamic_events
> > +
> > +if grep -q my_wprobe dynamic_events; then
> > + echo "Failed to remove wprobe event"
> > + exit_fail
> > +fi
>
> [Severity: Medium]
> Could this echo also trigger an early exit if removing the wprobe fails,
> bypassing the failure message?
Ditto.
Thanks,
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
next prev parent reply other threads:[~2026-08-30 5:35 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-22 9:22 [PATCH v13 00/12] tracing: wprobe: x86: Add wprobe for watchpoint Masami Hiramatsu (Google)
2026-08-22 9:22 ` [PATCH v13 01/12] kprobes: Protect kprobe_blacklist with RCU Masami Hiramatsu (Google)
2026-08-22 9:31 ` sashiko-bot
2026-08-22 9:22 ` [PATCH v13 02/12] x86/hw_breakpoints: Make DR7 updates NMI safe Masami Hiramatsu (Google)
2026-08-22 9:41 ` sashiko-bot
2026-08-30 5:35 ` Masami Hiramatsu
2026-08-22 9:22 ` [PATCH v13 03/12] x86/hw_breakpoints: Add arch_modify_local_hw_breakpoint_addr() API Masami Hiramatsu (Google)
2026-08-22 9:33 ` sashiko-bot
2026-08-22 9:23 ` [PATCH v13 04/12] HWBP: Add modify_local_hw_breakpoint_addr() API Masami Hiramatsu (Google)
2026-08-22 9:33 ` sashiko-bot
2026-08-22 9:24 ` [PATCH v13 05/12] tracing/wprobe: Add wprobe (watchpoint probe) trace event support Masami Hiramatsu (Google)
2026-08-22 9:49 ` sashiko-bot
2026-08-30 5:35 ` Masami Hiramatsu
2026-08-22 9:24 ` [PATCH v13 06/12] x86: hw_breakpoint: Add a kconfig to clarify when a breakpoint fires Masami Hiramatsu (Google)
2026-08-22 9:31 ` sashiko-bot
2026-08-22 9:24 ` [PATCH v13 07/12] selftests: tracing: Add a basic testcase for wprobe Masami Hiramatsu (Google)
2026-08-22 9:36 ` sashiko-bot
2026-08-30 5:35 ` Masami Hiramatsu [this message]
2026-08-22 9:24 ` [PATCH v13 08/12] selftests: tracing: Add syntax " Masami Hiramatsu (Google)
2026-08-22 9:35 ` sashiko-bot
2026-08-30 5:35 ` Masami Hiramatsu
2026-08-22 9:24 ` [PATCH v13 09/12] tracing/wprobe: Add set_wprobe and clear_wprobe event triggers Masami Hiramatsu (Google)
2026-08-22 9:42 ` sashiko-bot
2026-08-30 5:35 ` Masami Hiramatsu
2026-08-22 9:25 ` [PATCH v13 10/12] selftests: ftrace: Add wprobe trigger testcase Masami Hiramatsu (Google)
2026-08-22 9:39 ` sashiko-bot
2026-08-30 5:36 ` Masami Hiramatsu
2026-08-22 9:25 ` [PATCH v13 11/12] tracing/wprobe: Support BTF typecast in fetchargs Masami Hiramatsu (Google)
2026-08-22 9:40 ` sashiko-bot
2026-08-22 9:25 ` [PATCH v13 12/12] tracing/wprobe: Support BTF struct offset resolution in set_wprobe trigger Masami Hiramatsu (Google)
2026-08-22 9:51 ` sashiko-bot
2026-08-30 5:36 ` Masami Hiramatsu
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=20260830143532.0c2aee25c656896388e6bab7@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=sashiko-bot@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.