Re: [PATCH v2 00/12] Add build ID to stacktraces

2021-03-30 Thread Petr Mladek
On Thu 2021-03-25 16:21:46, Stephen Boyd wrote: > Quoting peter enderborg (2021-03-25 04:06:17) > > On 3/24/21 9:55 AM, Christoph Hellwig wrote: > > > On Tue, Mar 23, 2021 at 07:04:31PM -0700, Stephen Boyd wrote: > > >> x5 : x4 : 0001 > > >> x3 : 0008 x2 :

Re: [PATCH v2 00/12] Add build ID to stacktraces

2021-03-25 Thread Stephen Boyd
Quoting peter enderborg (2021-03-25 04:06:17) > On 3/24/21 9:55 AM, Christoph Hellwig wrote: > > On Tue, Mar 23, 2021 at 07:04:31PM -0700, Stephen Boyd wrote: > >> x5 : x4 : 0001 > >> x3 : 0008 x2 : ff93fef25a70 > >> x1 : ff93fef15788 x0 : ffe

Re: [PATCH v2 00/12] Add build ID to stacktraces

2021-03-25 Thread Stephen Boyd
Quoting peter enderborg (2021-03-25 04:14:31) > > el0_sync_compat_handler+0xa8/0xcc > > el0_sync_compat+0x178/0x180 > > ---[ end trace 3d95032303e59e68 ]--- > > How will this work with the ftrace? > It won't affect ftrace, if that's the question you're asking.

Re: [PATCH v2 00/12] Add build ID to stacktraces

2021-03-25 Thread peter enderborg
On 3/24/21 3:04 AM, Stephen Boyd wrote: > This series adds the kernel's build ID[1] to the stacktrace header printed > in oops messages, warnings, etc. and the build ID for any module that > appears in the stacktrace after the module name. The goal is to make the > stacktrace more self-contained an

Re: [PATCH v2 00/12] Add build ID to stacktraces

2021-03-25 Thread peter enderborg
On 3/24/21 9:55 AM, Christoph Hellwig wrote: > On Tue, Mar 23, 2021 at 07:04:31PM -0700, Stephen Boyd wrote: >> x5 : x4 : 0001 >> x3 : 0008 x2 : ff93fef25a70 >> x1 : ff93fef15788 x0 : ffe3622352e0 >> Call trace: >> lkdtm_WARNING+0x28/0x30 [

Re: [PATCH v2 00/12] Add build ID to stacktraces

2021-03-24 Thread Stephen Boyd
HTML mail? Quoting Konstantin Khlebnikov (2021-03-24 01:23:55) > 24.03.2021, 05:04, "Stephen Boyd" : >   > Looks too noisy for me. Maybe print id in the line "Modules linked in:"? > I suppose only out-of-tree modules need this? >   Please see this note in patch 4: Originally, I put this on the %

Re: [PATCH v2 00/12] Add build ID to stacktraces

2021-03-24 Thread Christoph Hellwig
On Tue, Mar 23, 2021 at 07:04:31PM -0700, Stephen Boyd wrote: > x5 : x4 : 0001 > x3 : 0008 x2 : ff93fef25a70 > x1 : ff93fef15788 x0 : ffe3622352e0 > Call trace: > lkdtm_WARNING+0x28/0x30 [lkdtm ed5019fdf5e53be37cb1ba7899292d7e143b259e] >

[PATCH v2 00/12] Add build ID to stacktraces

2021-03-23 Thread Stephen Boyd
This series adds the kernel's build ID[1] to the stacktrace header printed in oops messages, warnings, etc. and the build ID for any module that appears in the stacktrace after the module name. The goal is to make the stacktrace more self-contained and descriptive by including the relevant build ID