Re: [PATCH v6 00/13] Add build ID to stacktraces
From: Petr Mladek <pmladek@suse.com>
Date: 2021-05-11 14:22:03
Also in:
kexec, linux-arm-kernel, lkml
From: Petr Mladek <pmladek@suse.com>
Date: 2021-05-11 14:22:03
Also in:
kexec, linux-arm-kernel, lkml
On Tue 2021-05-11 12:58:47, David Laight wrote:
From: Steven Rostedtquoted
Sent: 11 May 2021 13:53 On Tue, 11 May 2021 12:36:06 +0000 David Laight [off-list ref] wrote:quoted
quoted
x1 : ffffff93fef15788 x0 : ffffffe3622352e0 Call trace: lkdtm_WARNING+0x28/0x30 [lkdtm ed5019fdf5e53be37cb1ba7899292d7e143b259e] direct_entry+0x16c/0x1b4 [lkdtm ed5019fdf5e53be37cb1ba7899292d7e143b259e] full_proxy_write+0x74/0xa4Is there any way to get it to print each module ID only once?If there's a trivial way to do that, then perhaps it should be done, but for now, this patch series isn't as obnoxious as the previous versions. It only affects stack traces, and I'm fine with that.True. Printing the id in the module list was horrid. The real downside is all the extra text that will overflow the in-kernel buffer. At least it shouldn't be extra lines causing screen wrap. Unless the variable names are long - hi rust :-)
Note that the ID is printed only when CONFIG_STACKTRACE_BUILD_ID is enabled. It will be used only by some distros/vendors that use it to download the debuginfo packages. Best Regards, Petr