From: Steven Rostedt <rostedt@goodmis.org>
To: "Masami Hiramatsu (Google)" <mhiramat@kernel.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v5 2/2] tracing: Show last module text symbols in the stacktrace
Date: Fri, 21 Mar 2025 12:52:03 -0400 [thread overview]
Message-ID: <20250321125203.61585a02@batman.local.home> (raw)
In-Reply-To: <174230516153.2909896.11459658533253319657.stgit@mhiramat.tok.corp.google.com>
On Tue, 18 Mar 2025 22:39:21 +0900
"Masami Hiramatsu (Google)" <mhiramat@kernel.org> wrote:
> +/**
> + * trace_adjust_address() - Adjust prev boot address to current address.
> + * @tr: Persistent ring buffer's trace_array.
> + * @addr: Address in @tr which is adjusted.
> + */
> +unsigned long trace_adjust_address(struct trace_array *tr, unsigned long addr)
> +{
> + struct trace_scratch *tscratch;
> + struct trace_mod_entry *entry;
> + long *module_delta;
> + int idx = 0, nr_entries;
> +
> + /* If we don't have last boot delta, return the address */
> + if (!(tr->flags & TRACE_ARRAY_FL_LAST_BOOT))
> + return addr;
> +
> + tscratch = tr->scratch;
> + /* if there is no tscrach, module_delta must be NULL. */
> + module_delta = READ_ONCE(tr->module_delta);
What protects this from being freed after it is read?
> + if (!module_delta || tscratch->entries[0].mod_addr > addr)
> + return addr + tr->text_delta;
> +
> + /* Note that entries must be sorted. */
> + nr_entries = tscratch->nr_entries;
> + if (nr_entries == 1 ||
> + tscratch->entries[nr_entries - 1].mod_addr < addr)
> + idx = nr_entries - 1;
> + else {
> + entry = __inline_bsearch((void *)addr,
> + tscratch->entries,
> + nr_entries - 1,
> + sizeof(tscratch->entries[0]),
> + cmp_mod_entry);
> + if (entry)
> + idx = entry - tscratch->entries;
> + }
> +
> + return addr + module_delta[idx];
> +}
> +
> #ifdef CONFIG_MODULES
> static int save_mod(struct module *mod, void *data)
> {
> @@ -6036,6 +6088,7 @@ static int save_mod(struct module *mod, void *data)
> static void update_last_data(struct trace_array *tr)
> {
> struct trace_scratch *tscratch;
> + long *module_delta;
>
> if (!(tr->flags & TRACE_ARRAY_FL_BOOT))
> return;
> @@ -6070,6 +6123,8 @@ static void update_last_data(struct trace_array *tr)
> return;
>
> tscratch = tr->scratch;
> + module_delta = READ_ONCE(tr->module_delta);
Say if a reader read tr->module_delta before the NULL write.
> + WRITE_ONCE(tr->module_delta, NULL);
>
> /* Set the persistent ring buffer meta data to this address */
> #ifdef CONFIG_RANDOMIZE_BASE
> @@ -6078,6 +6133,8 @@ static void update_last_data(struct trace_array *tr)
> tscratch->kaslr_addr = 0;
> #endif
> tr->flags &= ~TRACE_ARRAY_FL_LAST_BOOT;
> +
> + kfree(module_delta);
Why is this safe?
I don't see any synchronization between setting NULL and freeing this,
like RCU would do.
-- Steve
> }
>
next prev parent reply other threads:[~2025-03-21 16:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 13:39 [PATCH v5 0/2] tracing: Show last boot module symbols Masami Hiramatsu (Google)
2025-03-18 13:39 ` [PATCH v5 1/2] tracing: Fix a compilation error without CONFIG_MODULES Masami Hiramatsu (Google)
2025-03-18 13:39 ` [PATCH v5 2/2] tracing: Show last module text symbols in the stacktrace Masami Hiramatsu (Google)
2025-03-21 16:52 ` Steven Rostedt [this message]
2025-03-24 2:35 ` 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=20250321125203.61585a02@batman.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@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 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.