All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Jinchao Wang" <wangjinchao600@gmail.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [RFC PATCH v2 11/13] mm/kwatch: add debugfs control plane
Date: Fri, 17 Jul 2026 13:27:14 +0000	[thread overview]
Message-ID: <20260717132715.2897C1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260717130637.1903667-1-wangjinchao600@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Critical] Use-After-Free in kwatch context pool due to delayed kretprobe exit handlers
--

--- Patch [11]: [RFC PATCH v2 11/13] mm/kwatch: add debugfs control plane ---
commit 7abbeb0e0111172be94e0f025440e5d06358c7a1
Author: Jinchao Wang <wangjinchao600@gmail.com>

mm/kwatch: add debugfs control plane
    
Wire the pieces together behind a single debugfs file.
Add the Kconfig entry and hook mm/kwatch into the mm build.

> diff --git a/mm/kwatch/core.c b/mm/kwatch/core.c
> new file mode 100644
> index 0000000000000..d8526d5aae5cd
> --- /dev/null
> +++ b/mm/kwatch/core.c
[ ... ]
> @@ -0,0 +1,324 @@
> +static void kwatch_stop_watching(void)
> +{
> +	watching_active = false;
> +
> +	kwatch_anchor_stop();
> +	/* after kthread_stop: the dead thread cannot re-mark expiry */
> +	kwatch_anchor_clear_expired();
> +
> +	kwatch_probe_stop();
> +	synchronize_rcu();
> +	kwatch_tsk_ctx_release_wps();
> +	/*
> +	 * Waits for disarm IPIs and unregisters breakpoints: no #DB can
> +	 * reach the ctx pool once this returns.
> +	 */
> +	kwatch_hwbp_free();
> +	kwatch_tsk_ctx_free();

[Severity: Critical]
Is it possible for a sleeping task to access the context pool after it gets
freed here?

If a task enters a watched function that can sleep, it triggers the kretprobe
entry handler and goes to sleep. When the user stops watching, this code
unregisters the probe and calls synchronize_rcu(). Since the sleeping task is
not in an RCU read-side critical section, synchronize_rcu() can return without
waiting for the task to wake up.

The kwatch_ctx_pool is then freed. When the sleeping task eventually wakes up
and returns from the watched function, its kretprobe exit trampoline executes
kwatch_lifecycle_exit(). That exit handler calls kwatch_tsk_ctx_get(), which
dereferences the freed pool, resulting in a use-after-free regression.

> +}

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260717125023.1895892-1-wangjinchao600@gmail.com?part=11

  reply	other threads:[~2026-07-17 13:27 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-17 12:50 [RFC PATCH v2 00/13] mm/kwatch: dynamic hardware watchpoints for hunting memory corruption Jinchao Wang
2026-07-17 13:02 ` [RFC PATCH v2 01/13] arch: add HAVE_REINSTALL_HW_BREAKPOINT Jinchao Wang
2026-07-17 13:02 ` [RFC PATCH v2 02/13] x86/hw_breakpoint: Unify breakpoint install/uninstall Jinchao Wang
2026-07-17 13:15   ` sashiko-bot
2026-07-17 13:03 ` [RFC PATCH v2 03/13] x86/hw_breakpoint: Add arch_reinstall_hw_breakpoint Jinchao Wang
2026-07-17 13:03 ` [RFC PATCH v2 04/13] HWBP: Add modify_wide_hw_breakpoint_local() API Jinchao Wang
2026-07-17 13:21   ` sashiko-bot
2026-07-17 13:04 ` [RFC PATCH v2 05/13] mm/kwatch: add watch expression parser and dereference engine Jinchao Wang
2026-07-17 13:15   ` sashiko-bot
2026-07-17 13:04 ` [RFC PATCH v2 06/13] mm/kwatch: add lockless per-task context pool Jinchao Wang
2026-07-17 13:19   ` sashiko-bot
2026-07-17 13:04 ` [RFC PATCH v2 07/13] stacktrace: export stack_trace_save_regs() Jinchao Wang
2026-07-17 13:05 ` [RFC PATCH v2 08/13] mm/kwatch: add hardware breakpoint backend Jinchao Wang
2026-07-17 13:24   ` sashiko-bot
2026-07-17 13:05 ` [RFC PATCH v2 09/13] mm/kwatch: add probe lifecycle runtime Jinchao Wang
2026-07-17 13:20   ` sashiko-bot
2026-07-17 13:06 ` [RFC PATCH v2 10/13] mm/kwatch: add anchor thread for global watchpoints Jinchao Wang
2026-07-17 13:20   ` sashiko-bot
2026-07-17 13:06 ` [RFC PATCH v2 11/13] mm/kwatch: add debugfs control plane Jinchao Wang
2026-07-17 13:27   ` sashiko-bot [this message]
2026-07-17 13:07 ` [RFC PATCH v2 12/13] mm/kwatch: add KUnit tests for the watch expression parser Jinchao Wang
2026-07-17 13:07 ` [RFC PATCH v2 13/13] Documentation/dev-tools: document KWatch Jinchao Wang
2026-07-17 13:30   ` sashiko-bot
2026-07-17 13:41 ` [RFC PATCH v2 00/13] mm/kwatch: dynamic hardware watchpoints for hunting memory corruption Dave Hansen
2026-07-17 18:10   ` Borislav Petkov

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=20260717132715.2897C1F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=wangjinchao600@gmail.com \
    /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.