From: sashiko-bot@kernel.org
To: wen.yang@linux.dev
Cc: linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v7 03/14] rv: Add a KUnit test for the HA timer underflow
Date: Sun, 11 Oct 2026 19:52:58 +0000 [thread overview]
Message-ID: <sashiko-outbox-167426@kernel.org> (raw)
In-Reply-To: <cdaf33af866392428f1942cef4e442b1d106989c.1791745088.git.wen.yang@linux.dev>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] rcu: scoped_guard(rcu) drops lock prematurely, leaking RCU-protected pointer
--
commit 578060191fd58b6c308a14708ec520459063ef75
Author: Wen Yang <wen.yang@linux.dev>
rv: Add a KUnit test for the HA timer underflow
This commit adds a minimal per-object HA monitor called rvtest. It also
introduces a test to verify that the HA clock math does not underflow
when checking invariants and starting timers.
> diff --git a/kernel/trace/rv/rv_monitors_test.c b/kernel/trace/rv/rv_monitors_test.c
> index 3ad11195e664a..889a209f64358 100644
> --- a/kernel/trace/rv/rv_monitors_test.c
> +++ b/kernel/trace/rv/rv_monitors_test.c
[ ... ]
> +static void rv_test_rvtest_underflow(struct kunit *test)
> +{
> + struct ha_monitor *ha_mon;
> + struct da_monitor *da_mon;
> + const int id = 4242;
> +
> + prepare_test(test, &rvtest_mon);
> + da_handle_start_run_event(id, NULL, start_rvtest);
> +
> + scoped_guard(rcu)
> + da_mon = da_get_monitor(id, NULL);
> + KUNIT_ASSERT_NOT_NULL(test, da_mon);
> + ha_mon = to_ha_monitor(da_mon);
> +
> + /* Uptime below the budget: time_ns - expire_ns would underflow. */
> + ha_reset_clk_ns(ha_mon, clk_rvtest, 0);
[Severity: Medium]
Does this scoped_guard drop the lock prematurely?
Because there are no curly braces around the scoped_guard, the RCU read-side
critical section only covers the single assignment to da_mon. Immediately
after da_get_monitor() returns, the guard scope ends and the lock is
released.
However, da_mon and its container ha_mon are dynamically allocated
RCU-protected objects. They are extensively used outside the critical section
in the subsequent test steps.
For example, ha_reset_clk_ns(), ha_start_timer_ns(), and
ha_cancel_timer_sync() all dereference this pointer after the RCU read
lock has been dropped. Could this violate RCU lifetime rules and create a
use-after-free risk?
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1791745088.git.wen.yang@linux.dev?part=3
next prev parent reply other threads:[~2026-10-11 19:52 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-11 19:39 [PATCH v7 00/14] rv: Add task latency over budget RV monitor wen.yang
2026-10-11 19:39 ` [PATCH v7 01/14] rv: Force environment reset action on HA monitor start wen.yang
2026-10-11 19:39 ` [PATCH v7 02/14] rv: Fix ha_monitor timer and invariant underflow wen.yang
2026-10-11 19:39 ` [PATCH v7 03/14] rv: Add a KUnit test for the HA timer underflow wen.yang
2026-10-11 19:52 ` sashiko-bot [this message]
2026-10-12 7:47 ` kernel test robot
2026-10-12 9:27 ` kernel test robot
2026-10-12 11:18 ` kernel test robot
2026-10-11 19:39 ` [PATCH v7 04/14] rv: Disarm HA timers on the storage free path wen.yang
2026-10-11 19:51 ` sashiko-bot
2026-10-11 19:39 ` [PATCH v7 05/14] rv: Add a KUnit test for " wen.yang
2026-10-11 19:50 ` sashiko-bot
2026-10-11 19:39 ` [PATCH v7 06/14] rv: Make da_monitor_reset_hook and EVENT_NONE_LBL overridable wen.yang
2026-10-11 19:53 ` sashiko-bot
2026-10-11 19:39 ` [PATCH v7 07/14] rv: Introduce DA_MON_ALLOCATION_STRATEGY wen.yang
2026-10-11 19:57 ` sashiko-bot
2026-10-11 19:39 ` [PATCH v7 08/14] rv: Add per-object teardown hook da_extra_cleanup wen.yang
2026-10-11 19:54 ` sashiko-bot
2026-10-11 19:39 ` [PATCH v7 09/14] rv: Add generic uprobe infrastructure for RV monitors wen.yang
2026-10-11 19:49 ` sashiko-bot
2026-10-11 19:39 ` [PATCH v7 10/14] rv: Add tlob model DOT file wen.yang
2026-10-11 19:39 ` [PATCH v7 11/14] rv: Add tlob hybrid automaton monitor wen.yang
2026-10-11 19:58 ` sashiko-bot
2026-10-11 19:39 ` [PATCH v7 12/14] rv: Add KUnit tests for the tlob monitor wen.yang
2026-10-11 19:39 ` [PATCH v7 13/14] selftests/verification: Add tlob selftests wen.yang
2026-10-11 19:51 ` sashiko-bot
2026-10-11 19:39 ` [PATCH v7 14/14] selftests/ftrace: Walk up parent dirs to find test.d/functions wen.yang
2026-10-12 11:58 ` [PATCH v7 00/14] rv: Add task latency over budget RV monitor Gabriele Monaco
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=sashiko-outbox-167426@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=wen.yang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox