From: Petr Mladek <pmladek@suse.com>
To: Stephen Boyd <swboyd@chromium.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Jiri Olsa <jolsa@kernel.org>,
Alexei Starovoitov <ast@kernel.org>, Jessica Yu <jeyu@kernel.org>,
Evan Green <evgreen@chromium.org>,
Hsin-Yi Wang <hsinyi@chromium.org>,
Steven Rostedt <rostedt@goodmis.org>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
linux-doc@vger.kernel.org, Matthew Wilcox <willy@infradead.org>
Subject: Re: [PATCH v4 05/13] module: Add printk formats to add module build ID to stacktraces
Date: Tue, 13 Apr 2021 17:01:14 +0200 [thread overview]
Message-ID: <YHWyOhYZuLsbt2gB@alley> (raw)
In-Reply-To: <20210410015300.3764485-6-swboyd@chromium.org>
On Fri 2021-04-09 18:52:52, Stephen Boyd wrote:
> Let's make kernel stacktraces easier to identify by including the build
> ID[1] of a module if the stacktrace is printing a symbol from a module.
> This makes it simpler for developers to locate a kernel module's full
> debuginfo for a particular stacktrace. Combined with
> scripts/decode_stracktrace.sh, a developer can download the matching
> debuginfo from a debuginfod[2] server and find the exact file and line
> number for the functions plus offsets in a stacktrace that match the
> module. This is especially useful for pstore crash debugging where the
> kernel crashes are recorded in something like console-ramoops and the
> recovery kernel/modules are different or the debuginfo doesn't exist on
> the device due to space concerns (the debuginfo can be too large for
> space limited devices).
>
> diff --git a/include/linux/module.h b/include/linux/module.h
> index 59f094fa6f74..4bf869f6c944 100644
> --- a/include/linux/module.h
> +++ b/include/linux/module.h
> @@ -11,6 +11,7 @@
>
> #include <linux/list.h>
> #include <linux/stat.h>
> +#include <linux/buildid.h>
> #include <linux/compiler.h>
> #include <linux/cache.h>
> #include <linux/kmod.h>
> @@ -367,6 +368,9 @@ struct module {
> /* Unique handle for this module */
> char name[MODULE_NAME_LEN];
>
> + /* Module build ID */
> + unsigned char build_id[BUILD_ID_SIZE_MAX];
Do we want to initialize/store the ID even when
CONFIG_STACKTRACE_BUILD_ID is disabled and nobody would
use it?
Most struct module members are added only when the related feature
is enabled.
I am not sure how it would complicate the code. It is possible
that it is not worth it. Well, I could imagine that the API
will always pass the buildid parameter and
module_address_lookup() might do something like
#ifndef CONFIG_STACKTRACE_BUILD_ID
static char empty_build_id[BUILD_ID_SIZE_MAX];
#endif
if (modbuildid) {
if (IS_ENABLED(CONFIG_STACKTRACE_BUILD_ID))
*modbuildid = mod->build_id;
else
*modbuildid = empty_build_id;
IMHO, this is primary a call for Jessica as the module code maintainer.
Otherwise, I am fine with this patch. And it works as expected.
Best Regards,
Petr
next prev parent reply other threads:[~2021-04-13 15:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-10 1:52 [PATCH v4 00/13] Add build ID to stacktraces Stephen Boyd
2021-04-10 1:52 ` [PATCH v4 05/13] module: Add printk formats to add module " Stephen Boyd
2021-04-12 11:58 ` Andy Shevchenko
2021-04-12 19:29 ` Stephen Boyd
2021-04-13 10:56 ` Andy Shevchenko
2021-04-13 15:16 ` Petr Mladek
2021-04-13 20:10 ` Stephen Boyd
2021-04-13 22:36 ` Stephen Boyd
2021-04-13 15:01 ` Petr Mladek [this message]
2021-04-13 22:57 ` Stephen Boyd
2021-04-15 8:53 ` Petr Mladek
2021-04-15 13:04 ` Jessica Yu
2021-04-18 1:52 ` Stephen Boyd
2021-04-19 10:34 ` Jessica Yu
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=YHWyOhYZuLsbt2gB@alley \
--to=pmladek@suse.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=ast@kernel.org \
--cc=evgreen@chromium.org \
--cc=hsinyi@chromium.org \
--cc=jeyu@kernel.org \
--cc=jolsa@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=swboyd@chromium.org \
--cc=willy@infradead.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