From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH v6 1/1] tracing: Show last module text symbols in the stacktrace
Date: Wed, 26 Mar 2025 07:10:11 +0900 [thread overview]
Message-ID: <20250326071011.3c2c97ba3a441c1a5fca582f@kernel.org> (raw)
In-Reply-To: <20250325154955.5ed4fa33@gandalf.local.home>
On Tue, 25 Mar 2025 15:49:55 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> On Mon, 24 Mar 2025 23:34:52 +0900
> "Masami Hiramatsu (Google)" <mhiramat@kernel.org> wrote:
>
> > From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> >
> > Since the previous boot trace buffer can include module text address in
> > the stacktrace. As same as the kernel text address, convert the module
> > text address using the module address information.
> >
> >
> > Reported-by: kernel test robot <lkp@intel.com>
> > Closes: https://lore.kernel.org/oe-kbuild-all/202503112205.joXgt8gR-lkp@intel.com/
> > Closes: https://lore.kernel.org/oe-kbuild-all/202503112303.D7g66VSd-lkp@intel.com/
>
> FYI, You don't add "Reported-by" and "Closes" tags for kernel test robot
> reports for previous versions of a patch set.
>
> It even says that in the report:
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202503112205.joXgt8gR-lkp@intel.com/
>
> "not just a new version of the same patch/commit"
Ah, I got it. I missed that part.
Thanks!
>
>
> > Signed-off-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
> > ---
> > Changes in v6:
> > - Protect module_delta by RCU.
> > - Make nop make_mod_delta() for CONFIG_MODULES=n.
> > - Rebased on linux-trace/for-next.
> > Changes in v4:
> > - Move module_delta to trace_array again.
> > - Use bsearch for lookup module_delta.
> > - Revert the boolean logic to avoid '!',
> > - Fix !CONFIG_MODULES compile errors.
> > ---
> > kernel/trace/trace.c | 133 +++++++++++++++++++++++++++++++++++++++++--
> > kernel/trace/trace.h | 8 +++
> > kernel/trace/trace_output.c | 4 +
> > 3 files changed, 138 insertions(+), 7 deletions(-)
> >
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>
prev parent reply other threads:[~2025-03-25 22:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-24 14:34 [PATCH v6 0/1] tracing: Show last boot module symbols Masami Hiramatsu (Google)
2025-03-24 14:34 ` [PATCH v6 1/1] tracing: Show last module text symbols in the stacktrace Masami Hiramatsu (Google)
2025-03-25 19:49 ` Steven Rostedt
2025-03-25 22:10 ` Masami Hiramatsu [this message]
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=20250326071011.3c2c97ba3a441c1a5fca582f@kernel.org \
--to=mhiramat@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox