From: sashiko-bot@kernel.org
To: "Crystal Wood" <crwood@redhat.com>
Cc: linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v3 7/9] tracing/osnoise: Split out per-cpu variable resets
Date: Wed, 14 Oct 2026 02:39:14 +0000 [thread overview]
Message-ID: <sashiko-outbox-170741@kernel.org> (raw)
In-Reply-To: <20261014022640.695786-8-crwood@redhat.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] tracing/osnoise: unconditional osn_reset_cpu corrupts active tracer state
--
commit e7bd03b79c8b047561cc86479c9cbb434768ea94
Author: Crystal Wood <crwood@redhat.com>
tracing/osnoise: Split out per-cpu variable resets
Reset per-cpu state every time we stop a kthread or detach an fd, rather
than assume everything gets cleaned up properly, and avoiding the need
to explicitly zero individual fields.
> diff --git a/kernel/trace/trace_osnoise.c b/kernel/trace/trace_osnoise.c
> index 22263e08b968b..d799c400ed9b7 100644
> --- a/kernel/trace/trace_osnoise.c
> +++ b/kernel/trace/trace_osnoise.c
[ ... ]
> @@ -2695,13 +2691,12 @@ timerlat_fd_read(struct file *file, char __user *ubuf, size_t count,
> static int timerlat_fd_release(struct inode *inode, struct file *file)
> {
> struct fd_data *fdd = file->private_data;
> - struct osnoise_variables *osn_var;
> -
> - osn_var = cpu_osn_var(fdd->cpu);
> + struct osnoise_variables *osn_var = cpu_osn_var(fdd->cpu);
>
> mutex_lock(&osn_var->lock);
> if (fdd == osn_var->fdd)
> timerlat_fd_detach(fdd);
> + osn_reset_cpu(fdd->cpu);
[Severity: High]
Does this unconditionally call osn_reset_cpu() even when the file descriptor
was already detached?
If tracing is stopped and the active file descriptor is detached, userspace
can start a new tracing session. This sets osn_var->fdd to a new fdd and arms
a new hrtimer on the CPU.
If userspace subsequently closes the old, detached file descriptor,
timerlat_fd_release() executes, skips timerlat_fd_detach(), and
unconditionally calls osn_reset_cpu().
Could this trigger a WARN_ON(osn->fdd) and zero out the tlat->zero and
osn->zero structs of the newly active session, corrupting its queued hrtimer
and potentially causing memory corruption or a kernel panic?
> mutex_unlock(&osn_var->lock);
>
> kfree(fdd);
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261014022640.695786-1-crwood@redhat.com?part=7
next prev parent reply other threads:[~2026-10-14 2:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 2:26 [PATCH v3 0/9] tracing/osnoise: Synchronization fixes Crystal Wood
2026-10-14 2:26 ` [PATCH v3 1/9] tracing/osnoise: Variable cleanup Crystal Wood
2026-10-14 2:26 ` [PATCH v3 2/9] tracing/osnoise: Hold a ref on osn->kthread Crystal Wood
2026-10-14 2:26 ` [PATCH v3 3/9] tracing/osnoise: Per-cpu mutexes and fd detachment Crystal Wood
2026-10-14 2:26 ` [PATCH v3 4/9] tracing/osnoise: kthreads: Verify CPU after migrate_disable() Crystal Wood
2026-10-14 2:26 ` [PATCH v3 5/9] tracing/osnoise: start_kthread: Always check OSN_WORKLOAD Crystal Wood
2026-10-14 2:26 ` [PATCH v3 6/9] tracing/osnoise: Take trace_types_lock in timerlat_fd_open Crystal Wood
2026-10-14 2:26 ` [PATCH v3 7/9] tracing/osnoise: Split out per-cpu variable resets Crystal Wood
2026-10-14 2:39 ` sashiko-bot [this message]
2026-10-14 2:26 ` [PATCH v3 8/9] tracing/osnoise: Print taint message for timerlat Crystal Wood
2026-10-14 2:26 ` [PATCH v3 9/9] tracing/osnoise: Refuse timerlat fd open if tracer inactive Crystal Wood
2026-10-14 2:39 ` sashiko-bot
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-170741@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=crwood@redhat.com \
--cc=linux-trace-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox